graphql-ws: Subscriptions aren't re-submitted properly on reconnection after connection failures

Screenshot First websocket and its related subscriptions

Next valid connection with its related subscriptions:

As you can see, the second screenshot has much less subscriptions sent to the server.

Expected Behaviour

No subscriptions are lost while reconnecting to a server

Actual Behaviour

It managed to reconnect to the server properly but didn’t send the whole set of subscriptions

Debug Information

This seems to happen only when the websockets aren’t able to reconnect right away to a server. In my case: I restarted my server locally and because it’s using typescript and transpiling on the fly with babel, it takes a little while to restart properly. So to reproduce I just launched my client, my server and then restarted my server and waited.

I am joining a har file below that has content as well, you can open this in any Chromium browser (sadly Firefox doesn’t handle HAR with content yet) by dragging the file into your dev tools network panel.

It should load the whole story and you would be able to see my network at the moment of the bug happening.

websockets-operations-after-reconnection.har.zip

Further Information

As with the previous issue, please let me know if you need more information and/or help 🙏

Thank you again for your great work on this new library!