Fix ReadableStream controller double-close crash #940
Merged
+16
−3
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
Motivation and Context
When the server disconnects (as allowed by SEP-1699 for SSE polling), the fetch response body stream gets cancelled. This closes the ReadableStream controller, but the underlying Node PassThrough stream still emits its "end" event, which then tries to close the already-closed controller.
The fix:
closedflagcancel()callback to properly clean up the Node streamWith this fix + JSON fix in modelcontextprotocol/typescript-sdk#1184 the inspector works again:
How Has This Been Tested?
Tested locally with the everything-server via Streamable HTTP transport.
Breaking Changes
None
Types of changes
Checklist