Aymeric Augustin

Here's a neat StackOverflow answer from 7 years ago that says exactly what I said above: https://stackoverflow.com/questions/35820885/why-do-many-websocket-libraries-implement-their-own-application-level-heartbeats And here's a great blog post that goes into the details of a...

@barseghyanartur For the record, starting a bug report by telling people that their code is insane isn't the best way to get help. May I suggest "this is incorrect" or...

Workaround: run `django-admin migrate wagtailadmin zero --fake` then re-run `django-admin migrate wagtailcore zero`.

This is the sort of fix I expected when I filed this issue. Thank you very much!

I submitted changes to Sanic in November to prevent this issue: #2609. If you're sticking to an old version of Sanic, you have to stick to an old version of...

If Sanic's stability policies require fixing it for 21.12 LTS, I would recommend one of: - adding the constraint `websockets

The documentation for this is here: https://websockets.readthedocs.io/en/stable/howto/sansio.html I don't remember how uvicorn integrates websockets so I'm not sure how much work it would take to upgrade to the Sans-I/O implementation....

That can't be a WebSocket handshake response; it's unsupported in websockets. You aren't going to involve websockets anymore after sending such a response. You can ignore websockets and write directly...

Well, `reject` isn't going to be entirely helpful, because it wants to set Content-Length: https://github.com/aaugustin/websockets/blob/ba1ed7a65cc876ff4e0fcd4dd4711402836475e2/src/websockets/server.py#L505 If you want to rely as much as possible on public API to avoid breaking...

See #1927. It looks like an issue in the current implementation. If you're replacing it with a new implementation, you can safely bump the dependency.