Disable HTTP/2 for the BytePlus client to stop shared-stream disconnects#120
Merged
Conversation
BytePlus's ap-southeast edge terminates HTTP/2 connections aggressively, and httpcore treats an EOF on an h2 connection as fatal for every stream multiplexed on it — surfacing as flaky "Server disconnected" RemoteProtocolError failures that take down all in-flight ByteDance requests at once. Pin that client to HTTP/1.1 so a dead connection affects at most one request and stale sockets are detected before reuse. Other providers stay on HTTP/2; the failure is only observed on BytePlus. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012NXSZbLdC1sEJNmTcCszXc
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
2 participants
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.
BytePlus's ap-southeast edge terminates HTTP/2 connections aggressively, and httpcore treats an EOF on an h2 connection as fatal for every stream multiplexed on it — surfacing as flaky "Server disconnected" RemoteProtocolError failures that take down all in-flight ByteDance requests at once. Pin that client to HTTP/1.1 so a dead connection affects at most one request and stale sockets are detected before reuse. Other providers stay on HTTP/2; the failure is only observed on BytePlus.
Claude-Session: https://claude.ai/code/session_012NXSZbLdC1sEJNmTcCszXc