-
Notifications
You must be signed in to change notification settings - Fork 439
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
Integrating max retry attempts with client and changing the default retry attempts to 0 #2131
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2131 +/- ##
==========================================
+ Coverage 71.73% 72.00% +0.26%
==========================================
Files 101 101
Lines 11117 11168 +51
==========================================
+ Hits 7975 8041 +66
+ Misses 2813 2797 -16
- Partials 329 330 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
7c684ec
to
7b4b0e8
Compare
e2a912d
to
906b53a
Compare
7a546f7
to
883f67f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title appears misleading; should it be something like: "Changing the default retry attempts to 0". Also, in description we can add that "setting max retry attempts to 0 implies infinite retries".
Done |
Co-authored-by: Kislay Kishore <kislayk@google.com>
Description
Link to the issue in case of a bug fix.
#1476
Testing details
Tested flag with storage test bench server.
two retries occurred.
two retries occurred.
five retries occurred.
Infinite retries occurred.