[global, cli] fix: validate visible gpu ordinals - #83
Conversation
|
Warning Review limit reached
More reviews will be available in 1 minute and 40 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (15)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request implements early validation of visible GPU ordinals (gpu_ids) against the available device count and removes the automatic mutation of CUDA_VISIBLE_DEVICES in the blocking CLI mode. It updates documentation across various guides, plans, and reference files to clarify that gpu_ids represent visible device ordinals after any environment-level filtering. Additionally, new unit tests are introduced to verify that invalid GPU IDs are rejected early and that CUDA_VISIBLE_DEVICES remains unmodified during execution. I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Summary
--gpu-idsas visible ordinals without rewritingCUDA_VISIBLE_DEVICES.gpu_idsagainst the current visible device count before constructing keep workers.Verification
git diff --check HEAD~1..HEADPYTHONPATH=$PWD/src pytest tests/test_cli_thresholds.py tests/global_controller tests/mcp tests/utilities/test_gpu_monitor.py -q(100 passed, 1 skipped)PYTHONPATH=$PWD/src pytest tests -q(190 passed, 12 skipped)PYTHONPATH=$PWD/src mkdocs buildpre-commit run --all-filesLocal Review