-
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
resolver: document handling UpdateState errors by resolvers #6002
Conversation
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 updates!
@dfawley thanks for the feedback, I adapted it to your suggestions, please have a look again |
Extend the Godoc for resolver.ClientConn.UpdateState with a description of how resolvers should handle returned errors. The description is based on the explanation of dfawley in grpc#5048
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.
Thank you! For future reference, please do not perform force-pushes when updating PR comments, as this messes up github review comments and loses the history of the PR as it changed over time. This one was small enough that it doesn't matter, but it's a good general practice to follow.
Thanks for the change!
@zasweq please double-check and approve so we can merge this, thanks. |
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.
Extend the Godoc for resolver.ClientConn.UpdateState with a description of how resolvers should handle returned errors.
The description is based on the explanation of dfawley in #5048
RELEASE NOTES: