chore: update nixl to latest 0.3.1 commit

[nv-anants]

update nixl to latest 0.3.1 commit

closes: OPS-303

Summary by CodeRabbit

• Chores
  • Updated build process to use a newer commit for dependencies.
  • Changed dependency management to use a versioned crate from the registry instead of a specific Git commit.

[coderabbitai]

Walkthrough

This change updates the NIXL_COMMIT hash in a build script and modifies the nixl-sys dependency in a Cargo.toml file from a Git commit reference to a versioned crate. No logic or control flow is altered in the affected files.

Changes

File(s)	Change Summary
container/build.sh	Updated NIXL_COMMIT variable to a new commit hash.
lib/llm/Cargo.toml	Changed nixl-sys dependency from a Git commit reference to version 0.3.1 from the registry.

Possibly related PRs

• chore: update dynamo and nixl versions for 0.3.0 #1240: Updates the NIXL_COMMIT hash in container/build.sh, indicating a related change in nixl version pinning.
• chore: update dynamo and nixl versions for 0.3.1 #1517: Coordinates on version bumping for nixl and related packages, including nixl-sys in the workspace.
• fix: Fix NIXL 0.3.1 build #1561: Modifies the nixl-sys dependency declaration in the opposite direction (from crate version to Git commit).

Poem

A hash replaced, a crate aligned,
In scripts and tomls, versions signed.
The build hops forward, dependencies clear,
With every change, release draws near.
🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

container/build.sh (1)

117-117: Consider tracking Nixl by semver tag instead of hard-coding a commit SHA

Hard-pinning to a raw commit means you must touch this script every time nixl publishes a patch.
Because you already pull the crate nixl-sys = "0.3.1" via Cargo, you could instead:

1. git fetch --tags and checkout the annotated tag v0.3.1, or
2. Skip the checkout entirely and trust the crate artefact.

This removes one manual sync point and reduces the risk that the commit diverges from the crate’s code.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6901c7c and 7b10139.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• lib/bindings/python/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• container/build.sh (1 hunks)
• lib/llm/Cargo.toml (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: kthui
PR: ai-dynamo/dynamo#1424
File: lib/runtime/src/pipeline/network/egress/push_router.rs:204-209
Timestamp: 2025-06-13T22:07:24.843Z
Learning: The codebase uses async-nats version 0.40, not the older nats crate. Error handling should use async_nats::error::Error variants, not nats::Error variants.

lib/llm/Cargo.toml (1)

Learnt from: kthui
PR: ai-dynamo/dynamo#1424
File: lib/runtime/src/pipeline/network/egress/push_router.rs:204-209
Timestamp: 2025-06-13T22:07:24.843Z
Learning: The codebase uses async-nats version 0.40, not the older nats crate. Error handling should use async_nats::error::Error variants, not nats::Error variants.

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: pre-merge-rust (.)
• GitHub Check: pre-merge-rust (lib/bindings/python)
• GitHub Check: pre-merge-rust (lib/runtime/examples)
• GitHub Check: Build and Test - vllm

🔇 Additional comments (1)

lib/llm/Cargo.toml (1)

87-89: Dependency switch looks good – ensure lockfile regeneration

The move from a git ref to the published crate nixl-sys = "0.3.1" is the right call; Cargo will now pick up patch releases automatically (^0.3.1).
Just be sure to regenerate Cargo.lock in CI (cargo update -p nixl-sys) so downstream consumers aren’t stuck with the old git hash.