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

skizze-cli - Connection broken #107

Open
martinpinto opened this issue Jan 19, 2016 · 1 comment
Open

skizze-cli - Connection broken #107

martinpinto opened this issue Jan 19, 2016 · 1 comment

Comments

@martinpinto
Copy link
Contributor

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>  
@martinpinto
Copy link
Contributor Author

and after executing a command, the client just freezes.

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

No branches or pull requests

1 participant