We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Whenever the connection to skizze service is broken, the skizze-cli client continues working:
skizze> 2016/01/19 11:01:51 transport: http2Client.notifyError got notified that the client transport was broken EOF. 2016/01/19 11:01:52 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:3596: getsockopt: connection refused"; Reconnecting to "127.0.0.1:3596"
The messages keep popping up and don't stop.
Instead the following could happen:
skizze-cli client displays a more "user friendly" message that the connection to the skizze service has been lost (e.g. in Redis):
Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected>
The text was updated successfully, but these errors were encountered:
and after executing a command, the client just freezes.
Sorry, something went wrong.
No branches or pull requests
Whenever the connection to skizze service is broken, the skizze-cli client continues working:
The messages keep popping up and don't stop.
Instead the following could happen:
skizze-cli client displays a more "user friendly" message that the connection to the skizze service has been lost (e.g. in Redis):
The text was updated successfully, but these errors were encountered: