-
Notifications
You must be signed in to change notification settings - Fork 3
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
[feature] client does not handle disconnects #6
Comments
The connection is not invalidated for the next request? |
it breaks completely, every subsequent request just throws errors that it can't connect to the server even though it is running again. Only restarting the application helps. |
so once i make a call and no server is available it first throws errors and after that it wont stop throwing on subsequent request. If I however do not make a request while the server is down and it is back available again before the next, for some strange reasons everything works. We talk by the way about spawning, the handler just silently dies and does nothing anymore forever. |
The client here is specifically a bit low level and should just start failing once a connection dies as you can just start a new client. The worker library should be handling reconnects though. |
Actually am using the worker library, somehow targeted the wrong repo 😂 So no still the same. I will move this over there. |
This client currently does not handle disconnects, be it just a network error or the complete node fails.
The text was updated successfully, but these errors were encountered: