Skip to content

fix(py-client): Recover from exhausted resumable connection retries - #702

Closed
lcian wants to merge 1 commit into
mainfrom
fix/python-resumable-connect-retries
Closed

lcian wants to merge 1 commit into
mainfrom
fix/python-resumable-connect-retries

Conversation

@lcian

@lcian lcian commented Oct 21, 2026

Copy link
Copy Markdown
Member

Automatic resumable uploads now treat exhausted urllib3 connection retries as transient failures, allowing the upload loop to query the persisted offset and resume instead of canceling the upload. Recognizing ConnectTimeoutError also covers its connection-refused and DNS-resolution subclasses through the existing MaxRetryError unwrapping.

Regression tests exhaust all three urllib3 connection retries for each failure type and verify that the upload probes its offset and completes successfully.

@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.41%. Comparing base (9c859ab) to head (109cddb).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #702      +/-   ##
==========================================
+ Coverage   91.40%   91.41%   +0.01%     
==========================================
  Files         118      118              
  Lines       24551    24551              
==========================================
+ Hits        22441    22444       +3     
+ Misses       2110     2107       -3     
Components Coverage Δ
Rust Backend 94.87% <ø> (ø)
Rust Client 81.83% <ø> (ø)
Python Client 93.28% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@lcian lcian changed the title fix(python): Recover from exhausted resumable connection retries fix(py-client): Recover from exhausted resumable connection retries Oct 21, 2026
@lcian

lcian commented Oct 21, 2026

Copy link
Copy Markdown
Member Author

On second thought I'm not sure we should do this, we would be multiplying the retries.

@lcian lcian closed this Oct 21, 2026
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.

1 participant