Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Closing WebSocket in Durable Object results in Unhandled Promise Rejection: TypeError: WebSocket already closed
See original GitHub issueMiniflare version: 2.6.0
While closing the WebSocket from the client side, it is expected to close it in the Durable Object right after, otherwise it won’t be closed. So closing negotiation goes like: Client > DO > Client.
Miniflare however throws Unhandled Promise Rejection: TypeError: WebSocket already closed error when Durable Object tries to close the socket when the ‘close’ event is received from the client.
Apparently, with Miniflare the client is able to close the socket prematurely without waiting for the Durable Object to close the server socket first.
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey! 👋 Thanks for the repo! 🙂 I’m able to reproduce the issue, and will have a go at fixing this soon. 👍
Alright, I’ll prepare a repo for that.