Skip to content

fix(gaxi): retry connect errors over gRPC#3658

Merged
dbolduc merged 1 commit intogoogleapis:mainfrom
dbolduc:fix-gaxi-retry-connect-grpc
Oct 31, 2025
Merged

fix(gaxi): retry connect errors over gRPC#3658
dbolduc merged 1 commit intogoogleapis:mainfrom
dbolduc:fix-gaxi-retry-connect-grpc

Conversation

@dbolduc
Copy link
Copy Markdown
Member

@dbolduc dbolduc commented Oct 31, 2025

Fixes #3640

Classify connect errors as such. These are retryable even if a request is not idempotent.

This affects the StorageControl client.

@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.69%. Comparing base (aa500bd) to head (2b52efa).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3658      +/-   ##
==========================================
- Coverage   95.70%   95.69%   -0.02%     
==========================================
  Files         129      129              
  Lines        5170     5175       +5     
==========================================
+ Hits         4948     4952       +4     
- Misses        222      223       +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 18:48
@dbolduc dbolduc requested a review from a team October 31, 2025 18:48
@dbolduc dbolduc merged commit 06653f0 into googleapis:main Oct 31, 2025
28 checks passed
@dbolduc dbolduc deleted the fix-gaxi-retry-connect-grpc branch October 31, 2025 18:49
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.

DNS and connection errors should be retryable

2 participants