feat(up): add --gpu-availability flag to override GPU detection - #185
Conversation
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
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. Review rate limit: 0/1 reviews remaining, refill in 3 minutes and 40 seconds.Comment |
Allow users to force GPU availability to "true" or "false" instead of relying on Docker auto-detection, matching the official devcontainer CLI behavior. The override is threaded through both the single-container and compose code paths.
7db0c03 to
2afa8b9
Compare
Summary
--gpu-availabilityCLI flag todevsy upfor overriding GPU auto-detectiondetect(default, existing behavior),true(force available),false(force unavailable)--gpu-availabilityflag (P2 CLI parity, DEVSY-018)