You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 17, 2022. It is now read-only.
Using the connect() api I am having trouble when the websocket to the full node disconnects.
Now that in v0.1.17 the event-emitter bus is also returned by the connect() method, I am listening on errors and try to catch the ones that are "websocket disconnected" type. I then rerun the connect() method to yield a new client and work with that one but it seems to have deeper troubles in the pumpify/duplexify modules...
Where could this problem lie? Any plans on handling disconnects and maybe autoreconnect in the connect() api?
Using the
connect()
api I am having trouble when the websocket to the full node disconnects.Now that in v0.1.17 the event-emitter
bus
is also returned by theconnect()
method, I am listening on errors and try to catch the ones that are "websocket disconnected" type. I then rerun theconnect()
method to yield a new client and work with that one but it seems to have deeper troubles in the pumpify/duplexify modules...Where could this problem lie? Any plans on handling disconnects and maybe autoreconnect in the
connect()
api?My code to handle disconnect:
The text was updated successfully, but these errors were encountered: