Show timeout and conflicting settings #284
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two very small user-oriented changes.
On the CLI side there are a few things that can go wrong when attempting to connect. One is the port which if wrong will display this and only this for 30 seconds (or another if a different wait_until_available specified):
A user could specify RUST_LOG="debug" for more info (and considering adding that note as a hint inside the CLI) which shows the multiple connection failures as they happen but if not then it looks like it is just hanging. With a method to see the wait_until_available it could look something like this instead:
The error when tls_cert_data or tls_ca is wrong is good, it's just not spaced out and looks like this.
So change to this: