Fix MCP malformed response terminal errors#21
Open
fallintoplace wants to merge 1 commit into
Open
Conversation
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
1 participant
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
Malformed downstream MCP messages could make response forwarding exit without posting a terminal JSON-RPC error response back to the control plane. That left request/response callers waiting for a timeout instead of receiving an immediate structured failure.
This change reuses the existing terminal downstream error path when the MCP server returns:
Tests
go test ./pkg/dispatcher/internal -run 'TestProcessorForwardResponsesPostsTerminalErrorOn(NonResponseMessage|InvalidID|IDMismatch)'go test ./pkg/dispatcher/internal