Fix: Buffer stdout data to handle large/fragmented JSON responses #22
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.
This PR fixes an issue where the MCP client would fail to parse large or fragmented JSON responses from the server. Previously, the code assumed that each chunk received from stdout contained a complete JSON message, which is not guaranteed by Node.js streams. As a result, long responses could be split and cause parsing errors or incomplete logs.
Changes:
Added a buffer to accumulate data from stdout until a full message (ending with \n) is received.
Only complete messages are parsed and processed, preventing errors with large or split responses.
Why:
This change ensures robust handling of server responses, especially when dealing with large payloads, and prevents log truncation or JSON parsing errors.