reliability: bound ignored Rust subprocess deadlines - #740
Conversation
|
Warning Review limit reached
Next review available in: 39 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
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 |
After SIGTERM/SIGKILL, communicate with PROCESS_REAP_TIMEOUT_SECONDS so a stuck child cannot hang the parent. Align deadline tests with the bounded reap contract from the fail-first cleanup regression.
Why
Ignored Rust statistical-study shards and Cargo metadata lookups can hang without process-group cleanup. This lands bounded, operation-specific deadlines with fail-closed timeout evidence.
What
scripts/_subprocess_deadlines.pyand ignored Rust shard runner integrationRebased onto current main with re-rendered CHANGELOG (reopens closed #578 work).