This supersedes some of #294, leveraging changes in pycrdt-websocket v0.13.1.
In #290, we see cases where the y-websocket server becomes unusable anytime an exception is raised within the y-websocket server's task groups. We made changes in pycrdt-websocket so that these exceptions could optionally be logged instead of raised, thereby keeping the server running.
This PR leverages those changes so we can ensure that there serve is never blocked.
We need to bump the pycrdt-websocket minimum version to get these changes.
This supersedes some of #294, leveraging changes in pycrdt-websocket v0.13.1.
In #290, we see cases where the y-websocket server becomes unusable anytime an exception is raised within the y-websocket server's task groups. We made changes in pycrdt-websocket so that these exceptions could optionally be logged instead of raised, thereby keeping the server running.
This PR leverages those changes so we can ensure that there serve is never blocked.
We need to bump the pycrdt-websocket minimum version to get these changes.