fix(issue): runHeadless restarts on deterministic EXIT_ERROR without classification, looping through identical no-work state (headless.js:172)#6181
Conversation
… progress added deterministic no-work restart classification to suppress useless `EXIT_ERROR` restart loops.
… as timeout/error final summary/JSON status now reports deterministic no-work as `no-work-deterministic` instead of generic timeout/error.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✨ 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 |
🟢 PR Risk Report — LOW
Affected Systems
File Breakdown
|
|
🤖 Dispatched Agent prompt (click to expand) |
|
Summary
no-work-deterministic, verified via targeted headless-events tests.Bugs Addressed
Verification
Related Issue
Repo
gsd-build/gsd-2Branch
issue/5739-runheadless-restarts-on-deterministic-ex-1778892827