fix: prevent duplicate error and close events in WebSocket #4631
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #4628
When a WebSocket is closed before the connection is established, the
errorandcloseevents were being fired twice instead of once.Root Cause
The issue was caused by
onSocketClose()being called multiple times:ws.close()is called before connection, it triggers:closeWebSocketConnection→failWebsocketConnection→onSocketClose()failWebsocketConnectionagain →onSocketClose()againSolution
Added a
closeEventFiredflag to the WebSocket handler to prevent duplicate events from being fired.Changes
lib/web/websocket/websocket.js:closeEventFiredproperty to the Handler typedefcloseEventFired: falsein the handler object#onSocketClose()to prevent duplicate eventstest/websocket/issue-4628.js:Testing
Before Fix
After Fix
🤖 Generated with Claude Code