Skip to content

Conversation

@alexbumbacea
Copy link

We have a use case for messages larger than 1MB, hence making this configurable would help.
In order to discover the source of our problems we had to spend some time investigating, as errors were silently discarded. So we also included changes to improving surfacing errors .

Copy link
Contributor

@findleyr findleyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's discuss this change in #726. I'm not sure we shouldn't just remove the buffering.

@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from 91f93af to ee3d418 Compare December 24, 2025 21:59
@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from ee3d418 to 85a4340 Compare January 3, 2026 09:48
@alexbumbacea alexbumbacea changed the title mcp: improve http transports error handling and make buffer size configurable mcp: improve http transports error handling and make transport work with any size message Jan 3, 2026
@alexbumbacea
Copy link
Author

@findleyr current proposal (no fixed buffer size) approach is inline with most sdks. Can we get this merged?

@findleyr
Copy link
Contributor

findleyr commented Jan 9, 2026

@alexbumbacea sorry for the delay, will review tomorrow.

@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from 85a4340 to 7ba1c9a Compare January 12, 2026 10:44
@alexbumbacea
Copy link
Author

@findleyr all comments have been either replied to or addressed. are there any other concerns?

@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch 2 times, most recently from 3577e96 to 377a108 Compare January 14, 2026 07:19
@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from 377a108 to 8f634ce Compare January 15, 2026 10:28
@alexbumbacea
Copy link
Author

@findleyr is there anything else?

@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from 8f634ce to 9fc710b Compare January 20, 2026 13:42
@alexbumbacea
Copy link
Author

@findleyr can we get this merged?

@findleyr
Copy link
Contributor

@alexbumbacea very sorry, I thought I had merged this. Total oversight on my part.

@maciej-kisiel we may want to cherry-pick this into the release, or do a second prerelease.

@findleyr
Copy link
Contributor

Apologies again for this getting lost in the weeds: I think there are a few things that need to be addressed before merging.

@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from da1ac52 to d534f57 Compare January 28, 2026 17:04
@alexbumbacea alexbumbacea requested a review from findleyr January 28, 2026 17:06
@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from d534f57 to 0416a3a Compare January 30, 2026 07:30
@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from 0416a3a to 636995a Compare January 30, 2026 07:41
findleyr
findleyr previously approved these changes Feb 3, 2026
Copy link
Contributor

@findleyr findleyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like my comments were addressed. However could you please also address @maciej-kisiel's before we merge?

Thanks for this change, this is a good cleanup.

Co-authored-by: Maciej Kisiel <[email protected]>
@alexbumbacea alexbumbacea force-pushed the handling-large-messages-and-surface-errors branch from cfa78c5 to 3409d32 Compare February 3, 2026 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants