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
I have a cursorless subscription that doesn't have a high throughput like the firehose and as a result can go quiet for several minutes at a time. During that time the websocket closes meaning I have to reconnect, losing out on events. I'd like to not have to implement a cursor, nor do I really like having to constantly reconnect on closing. I would much rather the websocket ping/pong be properly handled.
To Reproduce
Steps to reproduce the behavior:
Create a subscription XRPC endpoint using the package. Consider hooking it up to something that produces an event every 2-5 minutes or so.
Create a client that subscribes to the endpoint. Monitor for closing and messages.
It's more likely that the socket will close before the message comes through.
Expected behavior
The xrpc-server package should be sending pings every 20 seconds or so to connected clients.
Details
Operating system: 6.12.1-arch1-1
Node version: 23.4.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a cursorless subscription that doesn't have a high throughput like the firehose and as a result can go quiet for several minutes at a time. During that time the websocket closes meaning I have to reconnect, losing out on events. I'd like to not have to implement a cursor, nor do I really like having to constantly reconnect on closing. I would much rather the websocket ping/pong be properly handled.
To Reproduce
Steps to reproduce the behavior:
It's more likely that the socket will close before the message comes through.
Expected behavior
The xrpc-server package should be sending pings every 20 seconds or so to connected clients.
Details
The text was updated successfully, but these errors were encountered: