fix: reattach a retried compile to the timed-out in-flight compile - #2034
Conversation
Store the timed-out RequestId under .uloop so a later uloop compile can reattach instead of starting a conflicting new compile. Co-authored-by: Cursor <cursoragent@cursor.com>
Probe get-compile-status with a short retry window, wait for or return the stored result without sending a new compile request, and update timeout NextActions to describe the reattach recovery path. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 (8)
✨ 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 |
Ready is editor-wide and unrelated to the pending RequestId, so prefer HasResult, abandon attach after three Ready&&!HasResult observations, and warn when --force-recompile is ignored during reattach. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
COMPILE_WAIT_TIMEOUT, a lateruloop compilereattaches to the in-flight or completed compile instead of starting a new one that hitsUNITY_SERVER_BUSY.User Impact
uloop compileafter a wait timeout started a new compile and was often rejected as busy while Unity was still compiling.Changes
.uloop/pending-compile-request.jsonon wait timeout (20-minute stale window aligned with Unity result retention).get-compile-statuswith up to 10s of retries, then attach/wait, return a stored result, or fall through per force-recompile / missing-result rules.COMPILE_WAIT_TIMEOUTNextActions for reattach; add attach vibe-log events and branch coverage tests.Verification
scripts/check-go-cli.shpassed.ULOOP_DEBUG=1and the local dist binary:--compile-wait-timeout-seconds 1 --force-recompile→COMPILE_WAIT_TIMEOUT+ pending record writtenuloop compile→ notUNITY_SERVER_BUSY; attached and cleared pending recorduloop compile→cli_compile_attach_resultwithstored_resultand no latercli_compile_request_prepared/cli_compile_request_send_result