This is the error message I get with webosockets 10.1, roughly one out of 20 times when a player moves to the next page:


closing handshake failed
Traceback (most recent call last):
  File "/root/venvotree/lib/python3.8/site-packages/websockets/legacy/server.py", line 239, in handler
    await self.close()
  File "/root/venvotree/lib/python3.8/site-packages/websockets/legacy/protocol.py", line 779, in close
    await asyncio.shield(self.close_connection_task)
  File "/root/venvotree/lib/python3.8/site-packages/websockets/legacy/protocol.py", line 1309, in close_connection
    self.transport.write_eof()
  File "/usr/lib/python3.8/asyncio/selector_events.py", line 964, in write_eof
    self._sock.shutdown(socket.SHUT_WR)
OSError: [Errno 107] Transport endpoint is not connected

This is the warning message I receive when I upgrate websockets from 10.1 to 10.2:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
otree 5.10.4 requires websockets==10.1, but you have websockets 10.2 which is incompatible.

Dilemma: using bug-prone websockets 10.1 or ignore warning?

That traceback doesn’t occur with websockets 10.2?

No, I have a hard time to understand IT fully. But it appears that 10.2. has a lot bugs fixed...

You can ignore the pip warning and see if 10.2 fixes the error.

Thanks so much for the swift and helpful reply. This is part of a project where we apply a Video Chat that adjusts automatically to group size. We will share code with you soon, if you're interested.