fix(review): release lease after close race - #163
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe orchestration now releases an acquired invocation lease when event reporting or revision validation fails. A regression test covers concurrent pull-request closure and confirms cancellation, single lease release, and no provider invocation. ChangesInvocation lease cleanup
Merge Risk: ⚪ Minimal · up to The change releases a review lease when closure occurs during acquisition, preventing the provider lane from remaining blocked until lease expiry; no actionable merge-blocking risk remains. Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
A pull request can close while the invocation lease acquire request is still in flight. The post-acquire revision check then cancels the review before provider execution, but previously skipped lease cleanup and blocked the provider lane until TTL expiry.
This change releases the acquired lease when any post-acquire revision check or progress event fails. The regression test reproduces closure after acquisition and verifies one release, no provider invocation, and a cancelled outcome.
E2E evidence: PadelApp PR #669 closed during review; PR #670 immediately afterward exhausted as required_provider_lane_busy because the late third lease remained active.
Summary by CodeRabbit