Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: conductor-oss/python-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: conductor-oss/python-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fix/http2-auto-fallback
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 4 files changed
  • 2 contributors

Commits on Jun 3, 2026

  1. Auto-fall back to HTTP/1.1 on HTTP/2 protocol errors 

    Long-lived HTTP/2 connections through some proxies/load balancers
(e.g. GCP Cloud Run, AWS ALB) can produce protocol-level errors
(GOAWAY storms, stale keep-alive resets). The existing self-healing
reset rebuilt another HTTP/2 client that hit the same wall, so the
poll loop could cycle reset->fail->reset and effectively stop polling
with no CPU/memory spike.

On a ProtocolError/ReadError/WriteError, if HTTP/2 is enabled, the
reset now downgrades to HTTP/1.1 for the remainder of the process
(sticky) instead of rebuilding HTTP/2. Default-on HTTP/2 behavior is
unchanged for healthy environments. Opt out of the fallback with
CONDUCTOR_HTTP2_AUTO_FALLBACK=false.

Applied to both the sync (rest.py) and async (async_rest.py) clients;
added unit tests for both.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    @manan164 @claude
    manan164 and claude committed Jun 3, 2026
    Configuration menu
    Copy the full SHA
    af07ce9 View commit details
    Browse the repository at this point in the history
Loading