fix: dynamic-code cancel and Editor shutdown no longer hang on stuck work#1753
Conversation
|
Warning Review limit reached
Next review available in: 36 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 Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (16)
✨ 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 |
|
LGTM (merge after required CI is green). Verified this umbrella contains exactly the four reviewed sub-PR squash merges (#1744 → 4506a7c, #1745 → 343e478, #1746 → 26d48e9, #1747 → cbe2662) and the diff against v3-beta matches the sum of the reviewed sub-PR diffs — no extra changes. The follow-ups section correctly carries all four umbrella notes (CommandRunner.Cancel, AssemblyBuilder sync WaitForExit with the main-thread call-site note, post-shutdown worker resurrection, reset-crossing ObjectDisposedException race). Pure unit tests were re-verified locally at each sub-PR head (scheduler 9/9, SharedRoslynCompilerWorker 8/8). |
Summary
ReadLineholding the session lockCommandRunner.Execute(ExecutionContext)entry point removed; raw syncExecutefallback viaExecuteInternalremainsUser Impact
Executepath, wait forever for stuck user code, or block domain reload/quit behind a stuck workerReadLine(up to ~30s)Sub-PRs (already merged into this branch)
Execute()fromWrapperTemplateso cancellation is not droppedCommandRunner.Execute(ExecutionContext)onlyShutdownAsync5s timeout; timeout completes shutdown and logs a warningSemaphoreSlimcompile gate; shutdown bypasses gateFollow-ups (not in this PR)
CommandRunner.Cancel()— pre-existing unused public candidate; leave unless requestedSharedRoslynCompilerWorkerAssemblyBuildersyncWaitForExit(may run on main thread during compile/prewarm)execute-dynamic-codecan fail withObjectDisposedExceptionon a disposed scheduler; consider retryable "server restarting" mapping laterVerification
uloop compilegreen on fix: shared Roslyn worker ReadLine no longer blocks Editor shutdown #1747 follow-upv3-beta)Test plan