[FTF-198] Send close code on react-web-cli panel unmount#128
[FTF-198] Send close code on react-web-cli panel unmount#128denissellu wants to merge 2 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughModifies AblyCliTerminal component to close WebSocket connections with code 4001 and reason "user-closed-panel" when unmounting, signaling intentional shutdown to enable server session cleanup. Adds test coverage for unmount cleanup behavior. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/react-web-cli/src/AblyCliTerminal.tsx (1)
3556-3564: Add close code and reason to secondary WebSocket cleanup for consistency.The secondary WebSocket at line 3563 closes without an explicit close code, defaulting to 1000, while the primary socket uses close code 4001 with reason "user-closed-panel" at line 2425. This inconsistency should be addressed.
Consider updating line 3563 to use an explicit close code and reason string (e.g.,
close(1000, "user-closed-panel")orclose(4001, "user-closed-panel")) to match the pattern established for primary socket cleanup. This ensures both sockets signal their closure to the server in the same manner.
📜 Review details
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
packages/react-web-cli/src/AblyCliTerminal.test.tsxpackages/react-web-cli/src/AblyCliTerminal.tsx
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/Development.mdc)
**/*.{ts,tsx}: Use TypeScript and follow best practice naming conventions
ESLint is used to ensure all code adheres best practices; ensure you check that all code passes the linter before concluding your work.
Files:
packages/react-web-cli/src/AblyCliTerminal.tsxpackages/react-web-cli/src/AblyCliTerminal.test.tsx
🧬 Code graph analysis (2)
packages/react-web-cli/src/AblyCliTerminal.tsx (1)
packages/react-web-cli/src/terminal-shared.ts (1)
debugLog(311-315)
packages/react-web-cli/src/AblyCliTerminal.test.tsx (1)
packages/react-web-cli/src/AblyCliTerminal.tsx (1)
AblyCliTerminal(3838-3841)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: auth-tests
- GitHub Check: session-tests
- GitHub Check: ui-tests
- GitHub Check: Cursor Bugbot
- GitHub Check: e2e-cli
🔇 Additional comments (2)
packages/react-web-cli/src/AblyCliTerminal.tsx (1)
2418-2426: LGTM - Clear intent and proper cleanup.The unmount logic correctly closes the WebSocket with code 4001 to signal intentional closure, and the guard condition properly checks for sockets that are still active (CONNECTING or OPEN states). The inline comment clearly documents the server-side cleanup behavior.
packages/react-web-cli/src/AblyCliTerminal.test.tsx (1)
2471-2514: LGTM - Comprehensive test coverage for unmount cleanup.The test suite appropriately covers both the standard unmount case (socket open → close with 4001) and the edge case where the socket is already closing. The test structure is clear and the assertions directly verify the implementation's behavior.
f7a6f37 to
59b61d0
Compare
| // This tells the server to cleanup immediately (no grace period) | ||
| debugLog("[AblyCLITerminal] Closing WebSocket on unmount."); | ||
| socketReference.current.close(); | ||
| socketReference.current.close(4001, "user-closed-panel"); |
There was a problem hiding this comment.
I believe the intention here is that if we send 4001 to the terminal server, it just should just remove the session immediately, rather than wait for natural timeout. This is fine in principle for when a user explicitly clicks something, but doing this here would force the close on any unmount, which could happen between pages? We certainly don't want to limit navigation options to just non-reloading.
3beadba to
f9e5862
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
f9e5862 to
dbb4dcb
Compare
…t graceful Unmount uses a normal close() so the server grace period preserves session resumability on navigation/reload. A new terminateSession() method on the AblyCliTerminalHandle ref sends close(4001, "user-closed-panel") for immediate server cleanup when the user explicitly closes the panel.
dbb4dcb to
6d67b86
Compare
See FTF-198 This PR ensures the terminal component signals session closure correctly over WebSocket, while preserving session resume on navigation/reload.
Companion server PR: https://github.com/ably/cli-terminal-server/pull/105
Problem
The original implementation sent close code
4001on every component unmount. This told the server to immediately destroy the session — but unmount also fires on page navigation and reloads, which brokeresumeOnReloadbehavior.Solution
close()with no special code, so the server's grace period applies and the session remains resumable.terminateSession()— a new method exposed on theAblyCliTerminalHandleref — sendsclose(4001, "user-closed-panel")for immediate server cleanup. The parent should call this before unmounting when the user explicitly closes the panel.Changes
AblyCliTerminal.tsxclose(); addedterminateSession()on the imperative handle for explicit 4001 closeAblyCliTerminal.test.tsxterminateSession()sends 4001Usage
Note
Low Risk
Small, isolated change to WebSocket close semantics plus unit tests; main risk is behavioral expectations around when sessions should be terminated vs resumable.
Overview
Preserves
resumeOnReloadby changingAblyCliTerminalunmount cleanup to perform a normalWebSocket.close()(no4001), so the server can apply its resume grace period.Adds an imperative
terminateSession()method onAblyCliTerminalHandlethat explicitly closes primary/secondary sockets withclose(4001, "user-closed-panel")for immediate server-side session cleanup, and introduces tests covering unmount close behavior, skipping close when alreadyCLOSING, andterminateSession()sending4001.Written by Cursor Bugbot for commit 1caa265. This will update automatically on new commits. Configure here.