Skip to content

Conversation

nv-anants
Copy link
Contributor

@nv-anants nv-anants commented Jul 29, 2025

Overview:

minor fixes to READMEs

closes: OPS-514

Summary by CodeRabbit

  • Documentation
    • Improved installation and development instructions in the main README, including added prerequisites, clearer setup steps, and enhanced formatting for better visibility.
    • Expanded and clarified the llama.cpp backend README with detailed installation guides for both CPU and GPU setups.

Copy link
Contributor

coderabbitai bot commented Jul 29, 2025

Walkthrough

Documentation updates were made to clarify and expand installation and development instructions for both the main project and the llama.cpp backend. These changes include additional prerequisite steps, improved formatting, expanded usage examples, and clearer guidance for both CPU and GPU setups. No source code or public API changes were introduced.

Changes

Cohort / File(s) Change Summary
Main README Updates
README.md
Clarified installation steps for SGLang and TensorRT-LLM engines, improved formatting, added PYTHONPATH export for development, and reformatted notes for better visibility.
llama.cpp Backend Documentation
components/backends/llama_cpp/README.md
Expanded installation and usage instructions for the llama.cpp backend, detailing both CPU and GPU setup options.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐇
A README refreshed with clarity bright,
Guides devs through the setup, day or night.
From SGLang to llama, each step now clear,
CPU or GPU, the path’s right here.
With tidy commands and notes in view,
Happy coding, from this rabbit to you!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
README.md (4)

170-174: Add a language identifier to satisfy markdown-lint and syntax highlighting

The fenced block that starts at line 170 lacks a language spec (MD040).
Add bash (or sh) so the linter passes and the snippet is rendered with proper colours.

-```
+```bash
 # Install libnuma
 apt install -y libnuma-dev

(While touching the block you may also prefix the apt command with sudo to avoid permission issues on most systems.)


179-181: Second fenced block also missing a language spec

Same MD040 issue for the snippet that shows how to launch the SGLang worker.

-```
+```bash
 # Note the '.worker' in the module path for SGLang
 python -m dynamo.sglang.worker --help

210-211: Mark TensorRT-LLM install snippet as Bash

Linter again flags the block; add a language tag.

-```
+```bash
 uv pip install ai-dynamo[trtllm]

281-286: Trailing whitespace trips the pre-commit hook

Lines 281-285 contain stray spaces after the backticks and at EOL, causing the trailing-whitespace hook to fail.
Delete the extra spaces to unblock CI.

-# For development, use␠
+# For development, use
 export PYTHONPATH="..."
 
-> [!Note]␠
+> [!Note]
components/backends/llama_cpp/README.md (1)

4-12: Fix fenced-block lint error and correct pip option order

  1. The code fence on line 4 needs a language tag (MD040).
  2. pip install -r --force-reinstall requirements.gpu.txt has the options reversed; -r must precede its filename.
-```
+# CPU-only install
+```bash
 # Install ai-dynamo llama.cpp backend (CPU Mode)
 pip install "ai-dynamo[llama_cpp]" 
 
 # [Optional] To build llama.cpp for CUDA (needs a recent pip)
-pip install -r --force-reinstall requirements.gpu.txt
+pip install --force-reinstall -r requirements.gpu.txt
+
 python -m dynamo.llama_cpp --model-path /data/models/Qwen3-0.6B-Q8_0.gguf [args]

Removing the trailing spaces in lines 5-10 will also clear the trailing-whitespace pre-commit error.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 195c4c4 and 7046ee3.

📒 Files selected for processing (2)
  • README.md (3 hunks)
  • components/backends/llama_cpp/README.md (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
components/backends/llama_cpp/README.md (1)

Learnt from: ptarasiewiczNV
PR: #2027
File: container/deps/vllm/install_vllm.sh:0-0
Timestamp: 2025-07-22T10:22:28.972Z
Learning: The --torch-backend=auto flag works with vLLM installations via uv pip install, even though it's not a standard pip option. This flag is processed by vLLM's build system during installation to automatically match PyTorch distribution with container CUDA versions.

README.md (2)

Learnt from: fsaady
PR: #1730
File: examples/sglang/slurm_jobs/scripts/worker_setup.py:230-244
Timestamp: 2025-07-03T10:14:30.570Z
Learning: In examples/sglang/slurm_jobs/scripts/worker_setup.py, background processes (like nats-server, etcd) are intentionally left running even if later processes fail. This design choice allows users to manually connect to nodes and debug issues without having to restart the entire SLURM job from scratch, providing operational flexibility for troubleshooting in cluster environments.

Learnt from: nnshah1
PR: #1444
File: tests/fault_tolerance/utils/metrics.py:30-32
Timestamp: 2025-07-01T13:55:03.940Z
Learning: The @dynamo_worker() decorator in the dynamo codebase returns a wrapper that automatically injects the runtime parameter before calling the wrapped function. This means callers only need to provide the non-runtime parameters, while the decorator handles injecting the runtime argument automatically. For example, a function with signature async def get_metrics(runtime, log_dir) decorated with @dynamo_worker() can be called as get_metrics(log_dir) because the decorator wrapper injects the runtime parameter.

🪛 markdownlint-cli2 (0.17.2)
components/backends/llama_cpp/README.md

4-4: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

README.md

178-178: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🪛 GitHub Actions: Pre Merge Validation of (ai-dynamo/dynamo/refs/pull/2170/merge) by nv-anants.
components/backends/llama_cpp/README.md

[error] 3-7: pre-commit hook 'trailing-whitespace' failed. Trailing whitespace was fixed in this file. Run 'pre-commit run --all-files' locally to reproduce.

README.md

[error] 3-7: pre-commit hook 'trailing-whitespace' failed. Trailing whitespace was fixed in this file. Run 'pre-commit run --all-files' locally to reproduce.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: pre-merge-rust (lib/runtime/examples)
  • GitHub Check: pre-merge-rust (lib/bindings/python)
  • GitHub Check: pre-merge-rust (.)
  • GitHub Check: Mirror Repository to GitLab
  • GitHub Check: Build and Test - vllm

@athreesh
Copy link
Contributor

LGTM, thanks for making these edits

@nv-anants nv-anants enabled auto-merge (squash) July 29, 2025 18:35
@nv-anants nv-anants merged commit a8cb655 into main Jul 29, 2025
11 of 12 checks passed
@nv-anants nv-anants deleted the anants/fix-readme branch July 29, 2025 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants