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):
Connecting to EdgeDB instance 'anything' at localhost:10700...
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:
Connecting to EdgeDB instance 'anything' at localhost:10700 (will try up to 30s)...
The error when tls_cert_data or tls_ca is wrong is good, it's just not spaced out and looks like this.
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: