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

client: surface connection errors to callers #3412

Closed
wants to merge 1 commit into from

Conversation

sethp-nr
Copy link
Contributor

@sethp-nr sethp-nr commented Mar 2, 2020

This commit allows blocking clients to receive a more informative error
message than "context deadline exceeded", which is especially helpful in
tracking down persistent client misconfiguration (such as an invalid TLS
certificate, an invalid server that's refusing connections, etc.)

See: #3406
Re-opened from #3410 to retry the CLA bot.

This commit allows blocking clients to receive a more informative error
message than "context deadline exceeded", which is especially helpful in
tracking down persistent client misconfiguration (such as an invalid TLS
certificate, an invalid server that's refusing connections, etc.)
@dfawley
Copy link
Member

dfawley commented Mar 6, 2020

Per my comments in #2031, I don't think we should make this change. It would be a behavior change that users may be relying upon.

In general, blocking dials aren't really recommended. Instead, a non-blocking dial should be performed, and we should work more on something like #2055, which could provide the detailed errors. Or, we should try to mark TLS errors as non-temporary, since they typically indicate a misconfiguration unlikely to resolve within the time-frame of a blocking dial operation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants