fix: stop Roslyn worker revive after server reset or reload shutdown#1763
Conversation
Advance a session lifecycle generation on full Shutdown so in-flight compile retries cannot restart the worker after reset/reload/quit, while process-only retry cleanup still allows a legitimate replacement start. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 27 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 selected for processing (3)
✨ 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
User Impact
EnsureWorkerReadybriefly resurrected a worker (stdin EOF self-exits; no lasting leak, but wrong lifecycle).Design
SharedRoslynCompilerWorkerSession(not sticky bool + GetRuntimeFacade clear).Shutdown()advances generation under the state lock, then kills the process.ShutdownProcessLockedalone does not advance generation (legitimate retry).TryCompileWithRetriesAsynccaptures generation via lock;EnsureWorkerReady/StartWorkerProcesscompare+start atomically under the same lock.shared_worker_lifecycle_closed.Out of scope (umbrella notes)
shared_worker_lifecycle_closedto PR 6-2 restarting NextActions if/when it becomes user-visible.Verification
uloop compile→ SuccessTest plan
StartProcessLockedfor the captured generationShutdownadvances generation and refuses stale startsMade with Cursor