chore: enable rust-analyzer for all features in dev container

[ziqifan617]

Overview:

Useful for features like block-manager

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated the development environment configuration to enhance Rust code analysis for contributors working in the dev container. This improves editor diagnostics and code intelligence during development. There are no changes to application behavior, performance, or user-facing features. Existing settings remain intact, with only a minor adjustment to support the new configuration. No action is required from end users.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

Walkthrough

Devcontainer VS Code configuration updated to enable Rust Analyzer cargo all features by setting rust-analyzer.cargo.allFeatures=true in .devcontainer/devcontainer.json. Existing files.insertFinalNewline retained with a trailing comma adjustment.

Changes

Cohort / File(s)	Summary
Devcontainer config .devcontainer/devcontainer.json	Added "rust-analyzer.cargo.allFeatures": true under settings; retained files.insertFinalNewline with trailing comma to accommodate new setting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: small qol improvements to devcontainer #1427 — Also adjusts rust-analyzer settings in .devcontainer/devcontainer.json, indicating a related configuration theme.

Poem

Hop hop, I tweak my den,
A carrot of config for Rusty zen.
All features bloom, analyzer sees,
Devcontainer breeze among the trees.
Tiny comma, tidy cheer—
Code grows crisp, spring is here! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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)

.devcontainer/devcontainer.json (1)

37-44: Optional: guard against heavier indexing/Clippy work with all features enabled.

All-features can significantly increase rust-analyzer indexing and clippy compile scope across workspace members and targets. If you see sluggishness or higher RAM/CPU in the container, consider limiting check targets while keeping IDE symbol visibility broad.

Suggested lightweight adjustment:

• Keep rust-analyzer.cargo.allFeatures=true for IDE features.
• Limit on-save checks to primary library/bin targets (skip tests/examples/benches) to avoid full rebuilds.

Apply this optional change near the existing rust-analyzer settings:

@@
   "rust-analyzer.checkOnSave.command": "clippy",
   "rust-analyzer.checkOnSave.enable": true,
@@
-  "files.insertFinalNewline": true,
-  "rust-analyzer.cargo.allFeatures": true
+  "files.insertFinalNewline": true,
+  "rust-analyzer.cargo.allFeatures": true,
+  "rust-analyzer.check.allTargets": false

If you prefer, I can also stage a variant that uses a curated feature set for specific crates instead of allFeatures, but I understand the current goal is “enable everything” for developer convenience—confirm which direction you want.

Also applies to: 45-53, 55-56

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ea391f3 and 63cf3b8.

📒 Files selected for processing (1)

• .devcontainer/devcontainer.json (1 hunks)

⏰ 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). (1)

• GitHub Check: Build and Test - dynamo

🔇 Additional comments (2)

.devcontainer/devcontainer.json (2)

56-56: Enabling all Cargo features in rust-analyzer meets the PR objective.

Setting rust-analyzer.cargo.allFeatures to true aligns with the intent to surface symbols behind optional features (e.g., block-manager). No correctness concerns with the JSONC here.

---

55-55: Minor JSONC maintenance tweak looks good.

files.insertFinalNewline remains true and the preceding comma placement is valid in this JSON-with-comments context.