Skip to content

feat(gax): introduce connect error#3654

Merged
dbolduc merged 1 commit intogoogleapis:mainfrom
dbolduc:feat-gax-connect-error
Oct 31, 2025
Merged

feat(gax): introduce connect error#3654
dbolduc merged 1 commit intogoogleapis:mainfrom
dbolduc:feat-gax-connect-error

Conversation

@dbolduc
Copy link
Copy Markdown
Member

@dbolduc dbolduc commented Oct 31, 2025

Part of the work for #3640

Introduce a connection error kind, which is distinct from is_io().

Note that if we think is_connect() should imply is_transport(), we can always change the internal representation later.

@codecov
Copy link
Copy Markdown

codecov bot commented Oct 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.92%. Comparing base (9f533e9) to head (d524638).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3654      +/-   ##
==========================================
+ Coverage   95.89%   95.92%   +0.02%     
==========================================
  Files         128      128              
  Lines        5145     5152       +7     
==========================================
+ Hits         4934     4942       +8     
+ Misses        211      210       -1     

☔ View full report in Codecov by Sentry.
📢 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.

@dbolduc dbolduc marked this pull request as ready for review October 31, 2025 15:08
@dbolduc dbolduc requested a review from a team October 31, 2025 15:08
@dbolduc dbolduc merged commit 7d399d2 into googleapis:main Oct 31, 2025
28 checks passed
@dbolduc dbolduc deleted the feat-gax-connect-error branch October 31, 2025 15:14
dbolduc added a commit that referenced this pull request Oct 31, 2025
Part of the work for #3640

This PR effectively starts retrying connect errors, for non-idempotent
operations, by default, in GAPICs.

Note that we marked connect errors as `is_transient_and_before_rpc` in
#3654. Thus, connect errors would be retried by the default retry
policy(`Aip194Strict`)...

... if they existed. But we did not ever classify an error as connect.
This PR starts classifying the HTTP connect errors as such.
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.

2 participants