-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
client: return helpful error message when wait-for-ready RPCs fail with timeout #2777
Conversation
Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement. After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.
Regards, |
@xiang90 PTAL |
("I signed it") |
@menghanl PTAL |
6727225
to
816aae4
Compare
816aae4
to
27a8866
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.
Thanks for the fixes. Overall LGTM. One small change.
27a8866
to
32875ab
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.
Can you also add a test for it? It should be very similar with TestFailFastRPCErrorOnBadCertificates
You can make a copy of TestFailFastRPCErrorOnBadCertificates
, (and call the new one TestWaitForReadyRPCErrorOnBadCertificates
maybe).
In the test, change the RPC tc.EmptyCall
to an wait-for-ready RPC with a short timeout, and make sure the returned error contains the expected string.
32875ab
to
c87c1f4
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.
LGTM. Thanks for the fix!
FailFast(false)
, return helpful error message when context is time out
@menghanl Will this be included in the next release? Is there a scheduled release date? Thanks! |
Yes, the next release is scheduled at May 21. |
No description provided.