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
Current implementation of subscriptions using the websocket provider show the following behavior:
Create a subscription i.e. for new blocks. Do nothing else.
Ensure new blocks are being received.
Take the net connectivity down.
As there are no other packets to send through the provider, the subscription never errores out.
Take the connectivity up again.
The subscription never reconnects as it never detected the error condition.
Is there any plan or any idea on how to implement some kind of keepalive packages so the disconnection is detected by the subscription manager and timely notify the error to the lib user?
The text was updated successfully, but these errors were encountered:
Current implementation of subscriptions using the websocket provider show the following behavior:
Is there any plan or any idea on how to implement some kind of keepalive packages so the disconnection is detected by the subscription manager and timely notify the error to the lib user?
The text was updated successfully, but these errors were encountered: