Aymeric Augustin

Partial support would be better than no support at all, indeed. However, since there's a working PoC in #422 that does what you said and is merely missing error handling...

> It would have been far better to say something like "I'm not willing to spend time on this, but PRs are welcome". @nyuszika7h This is basically what the last...

Does https://websockets.readthedocs.io/en/stable/howto/faq.html#what-does-connectionclosederror-no-close-frame-received-or-sent-mean help? You didn't provide the full stack track but I suspect that's what you're hitting. If you understand why the server closes the connection, then you can avoid...

Yes, it's very odd that adding `await asyncio.sleep(0)` changes the behavior. I would like to understand why that is. Specifically, I would like to understand if the problem is on...

It is possible that f761e23 will reduce `AttributeError` related to `transfer_data_task`, if it happened when shutting down the server. If you have a stack trace for that error around, I...

One possibility for ``zlib.error`` would be: a buggy client negotiates ``client_max_window_bits`` but then doesn't honor it i.e. uses a larger compression window than what it declared. This would also be...

The ``ssl.SSLError`` look like I/O errors; I think I could add them to the clause handling `ConnectionError, TimeoutError, EOFError`.

I just pushed some changes to ignore errors that we can't do much about anyway. So, on the four cases you reported, the situation is the following: 1. AttributeError on...

OK, I suspect I haven't fixed this case. Can you provide the context of `/srv/Backend/Engine/protocol.py` around line 29?

That's a very good point. The current design doesn't make it easy to implement this because it separates strongly the opening handshake (where you could return a 404) from the...