fix(issue): assessInterruptedSession hides stale crash locks with matching PID, preventing startAuto cleanup#6175
Conversation
…ching PID, preventing startAuto cleanup
|
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 (2)
✨ 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
|
Summary
assessInterruptedSessionnow keeps stale crash locks even for same PID and only treats non-self alive PIDs as running, verified by focused interrupted-session auto tests.Verification
Related Issue
Repo
gsd-build/gsd-2Branch
issue/5714-assessinterruptedsession-hides-stale-cra-1778892835