We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
@dbolduc noted:
observation: in the (rare) exhausted before start case, the error message is a bit redundant:
Retry policy exhausted in <location>: Retry policy exhausted before first request attempt
I am fine with this.
Originally posted by @dbolduc in #12301 (comment)
and @devbww noted that we repeat "in" in the input to RetryLoopError().
RetryLoopError()
I think we need to create separate functions to return different errors, e.g.:
Status RetryLoopErrorNonIdempotent(Status s, char const* location); Status RetryLoopErrorFinal(Status s, char const* location, bool exhausted);
In the body of these functions we can implement the formatting as needed.
We should also consider adding information in ErrorInfo() to indicate the type of failure in some kind of machine-consumable form.
ErrorInfo()
The text was updated successfully, but these errors were encountered:
coryan
Successfully merging a pull request may close this issue.
@dbolduc noted:
observation: in the (rare) exhausted before start case, the error message is a bit redundant:
I am fine with this.
Originally posted by @dbolduc in #12301 (comment)
and @devbww noted that we repeat "in" in the input to
RetryLoopError()
.I think we need to create separate functions to return different errors, e.g.:
In the body of these functions we can implement the formatting as needed.
We should also consider adding information in
ErrorInfo()
to indicate the type of failure in some kind of machine-consumable form.The text was updated successfully, but these errors were encountered: