Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(GCS+gRPC): scale timeout for downloads #14430

Merged
merged 2 commits into from
Jul 3, 2024

Conversation

coryan
Copy link
Contributor

@coryan coryan commented Jul 3, 2024

The progress timeouts need to be scaled because the data arrives in
quantums on (roughly) 2MiB blocks.


This change is Reviewable

The progress timeouts need to be scaled because the data arrives in
quantums on (roughly) 2MiB blocks.
@coryan coryan marked this pull request as ready for review July 3, 2024 12:39
@coryan coryan requested review from a team as code owners July 3, 2024 12:39
Copy link

codecov bot commented Jul 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.58%. Comparing base (b5026cc) to head (f295979).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #14430      +/-   ##
==========================================
- Coverage   93.58%   93.58%   -0.01%     
==========================================
  Files        2313     2313              
  Lines      206884   206891       +7     
==========================================
+ Hits       193615   193616       +1     
- Misses      13269    13275       +6     

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

@coryan coryan merged commit 8ef423c into googleapis:main Jul 3, 2024
63 checks passed
@coryan coryan deleted the fix-GCS+gRPC-timeouts-for-downloads branch July 3, 2024 15:38
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