Bug: Missing WebSocket Connection State Validation on Close and Message Send Operations
Description
The current WebSocket implementation in Litestar lacks connection state validation for critical operations. When attempting to close a connection, there is no check to verify if the connection has already been closed. Similarly, when sending messages, the implementation doesn't validate whether the connection is still active before attempting transmission. This can lead to attempts to perform operations on closed connections and potential application errors.
This is especially noticeable under heavy loads
URL to code causing the issue
No response
MCVE
# Your MCVE code hereSteps to reproduce
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See errorScreenshots
""Logs
No response
Litestar Version
latest
v2.12
Platform
- Linux
- Mac
- Windows
- Other (Please specify in the description above)
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too