[WIP] Investigate failing test in PR #1100 #1104
Closed
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.
Investigation and Fix for PR #1100 ✅
Summary
Successfully fixed the failing test in PR #1100 by addressing the underlying "write after end" error and applying the PR's test improvements.
Root Cause Analysis
The test failure occurred because:
_detachSocket()to simulate network disconnectionsockettonullbut left timers running in stream-managemententity.send()which tried to write to the null socketChanges Made
1. packages/connection/index.js
Added null check before writing to socket:
2. test/stream-management.test.js
server.enableModules(["smacks"])tobeforeAllhookbeforeEachhook for server restartafterAllwith try/finally for robust error handlingSecurity Summary
✅ CodeQL scan passed with no alerts
✅ No vulnerabilities introduced by changes
The fix makes the error handling more robust and prevents confusing "write after end" errors when the socket is disconnected.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.