I'm having this issue pop up when using PocketSocket, but it's not 100% reproducible. Seems to be somehow timing related. For context, I'm using the library to help unit test a web socket consumer library, so we start/stop the web socket server before/after each test. This error doesn't always happen, but seems to happen enough that it's causing us some issues.
Let me know if there's more information I can give you to help in tracking this down.
I'm having this issue pop up when using PocketSocket, but it's not 100% reproducible. Seems to be somehow timing related. For context, I'm using the library to help unit test a web socket consumer library, so we start/stop the web socket server before/after each test. This error doesn't always happen, but seems to happen enough that it's causing us some issues.
Let me know if there's more information I can give you to help in tracking this down.