You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since websockets==14.0, they changed the backend to a "new" asyncio implementation, changing the default value of max_queue from None to 16. This causes troubles in high-traffic connections, as they can't be properly closed and remain stuck.
In order to avoid this, max_queue can be set back to None temporarily, as the documentation of websockets states that this is not recommended.
Since the cancellation error seems to be some kind of buffer overflow or other kind of trouble, I already created an issue at python-websockets/websockets#1555, which hopefully get addressed soon.
The text was updated successfully, but these errors were encountered:
Since websockets==14.0, they changed the backend to a "new" asyncio implementation, changing the default value of
max_queue
fromNone
to 16. This causes troubles in high-traffic connections, as they can't be properly closed and remain stuck.In order to avoid this,
max_queue
can be set back toNone
temporarily, as the documentation of websockets states that this is not recommended.Since the cancellation error seems to be some kind of buffer overflow or other kind of trouble, I already created an issue at python-websockets/websockets#1555, which hopefully get addressed soon.
The text was updated successfully, but these errors were encountered: