mcp: preserve SSE events buffered after the endpoint - #1270
Merged
guglielmo-san merged 1 commit intoSep 15, 2026
Merged
guglielmo-san merged 1 commit into
guglielmo-san merged 1 commit into
Conversation
Reuse the event scanner across endpoint discovery and message reading so that events already buffered after the endpoint are retained. Add a regression test for coalesced events and a separate-delivery control.
guglielmo-san
approved these changes
Sep 15, 2026
Contributor
|
@yyydddkkk thank you for the contribution! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SSEClientTransport.Connect creates one event scanner to read the endpoint event
and a second scanner to read subsequent messages. Each scanner owns a buffered
reader, so bytes read ahead by the first scanner are discarded when it is
abandoned. A message coalesced with the endpoint can therefore disappear while
the connection remains open.
Reuse the event scanner across the endpoint handshake and the message-reading
goroutine. This preserves unread bytes without changing the public API.
The regression test exercises Connect and Read with a controlled HTTP response
body, covering both a message coalesced with the endpoint and a message arriving
after Connect returns. On unmodified main, the separate-message control passes
and the coalesced case times out; both pass with the fix.
Validation on linux/amd64 with Go 1.26.8:
The HTTP response boundary is simulated; no third-party server or proxy was
used. This change concerns the legacy SSE transport. The Streamable HTTP
conformance suite was not run.