[WRONG BRANCH] fix(server): bound live sideband lease cleanup - #39
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
⏳ DRAFT
What to do
Its title has been prefixed with |
|
✅ Deterministic PR hygiene checks passed. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe Live sideband close fallback now performs forced local cleanup after a bounded upstream close retry. The drain test verifies that main-profile ownership is released and a profile switch returns status 200. ChangesLive sideband cleanup
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Motivation
Description
armLiveSidebandCloseFallbackinsrc/server/index.tsto force local finalization after the bounded retry instead of only finalizing when the upstream reportsCLOSED.closeLiveSidebandcomments and fallback behavior so the fallback performs a retry and then releases local sideband state if the upstream never completes the handshake.src/server/ws-bridge.tsdocumentation to reflect the bounded forced-cleanup semantics forliveCloseFallback.tests/native-profile-drain-server.test.tsto assert that an uncooperative upstream no longer pins native-main ownership and that a profile switch can proceed after the fallback.Testing
bun run typecheck, which completed successfully.bun run test; the modified native-profile drain scenarios passed, including the updated uncooperative-upstream regression, while the overall suite exhibited unrelated timeouts/failures in a different test (management-provider-validation).bun run privacy:scan, which passed.bun test tests/native-profile-drain-server.test.tsdirectly in this environment failed due to a local Bun/runtime mismatch (node:zlibexport), but the repository test wrapper (bun run test) exercised and validated the focused changes.Codex Task
Summary by CodeRabbit