Ending a websocket handler does not close the websocket

[wiggzz]

I am not sure if this is an issue or not but I can't find much information on the expected behavior (and this may well be the responsibility of FastAPI). But it seems that when the asgi handler for a websocket ends, the websocket is not closed gracefully. This can result in a client staying connected even though the server handler is no longer running. My expectation is that when the handler ends, the websocket client should be notified with a close message since nothing more can happen there.

Reproducer here https://github.com/wiggzz/websocket-disconnect

[Kludex]

Hmmm... I think I noticed this some time ago, and I was supposed to merge this: #2332

[wiggzz]

@Kludex are you planning to merge that?