version requirement for websockets/update websockets code #108

Open
opened 2026-03-30 04:52:37 +00:00 by villac · 2 comments

Websockets 16.0, released in January 10, 2026, breaks CAT-SOOP. There are non-backwards compatible changes that prevent an instance from starting up. Until code can be updated to reflect the new changes, there should be a hard version requirement to prevent installing websockets >=16.0.

Websockets 16.0, released in January 10, 2026, breaks CAT-SOOP. There are non-backwards compatible changes that prevent an instance from starting up. Until code can be updated to reflect the new changes, there should be a hard version requirement to prevent installing websockets >=16.0.
Owner

I can't replicate this on the current main branch (which seems to be working fine with websockets v16). I could imagine the lts-19 branch having trouble with it, but there I have websockets==12.0 in the requirements.txt.

Can you share some more info about how you're running this and, e.g., what kind of error message you're getting?

I can't replicate this on the current main branch (which seems to be working fine with `websockets` v16). I could imagine the `lts-19` branch having trouble with it, but there I have `websockets==12.0` in the `requirements.txt`. Can you share some more info about how you're running this and, e.g., what kind of error message you're getting?
Author

Sorry I think this is actually be a false alarm. It looks like this is only an issue when installing older versions of CAT-SOOP. The most recent version has the requirement you had mentioned, so there is no issue.

I had done the following:

  1. Create new venv
  2. pip install catsoop=19.0.6
  3. try to start up catsoop instance (catsoop start)
  4. error:RuntimeError: no running event loop
    [start_catsoop.py 1624894] reporter!r (pid 1625672) died. restarting.
    Traceback (most recent call last):
    File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/catsoop/scripts/reporter.py", line 136, in
    start_server = websockets.serve(reporter, "0.0.0.0", PORTNUM)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/websockets/asyncio/server.py", line 759, in init
    self.server = Server(
    ^^^^^^^
    File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/websockets/asyncio/server.py", line 284, in init
    self.loop = asyncio.get_running_loop()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^

I also tried the above steps but with most recent catsoop. The requirement of websockets==12.0 prevents this issue. A forced upgrade to 16.0 reproduces this error, but there is only select reasons why that may be necessary. An extra note from my own usage: I was able to safely upgrade to 15.0.1 to satisfy additional dependencies for software used in conjunction with catsoop.

Sorry I think this is actually be a false alarm. It looks like this is only an issue when installing older versions of CAT-SOOP. The most recent version has the requirement you had mentioned, so there is no issue. I had done the following: 1. Create new venv 2. pip install catsoop=19.0.6 3. try to start up catsoop instance (catsoop start) 4. error:RuntimeError: no running event loop [start_catsoop.py 1624894] reporter!r (pid 1625672) died. restarting. Traceback (most recent call last): File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/catsoop/scripts/reporter.py", line 136, in <module> start_server = websockets.serve(reporter, "0.0.0.0", PORTNUM) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/websockets/asyncio/server.py", line 759, in __init__ self.server = Server( ^^^^^^^ File "/home/bob/python-venvs/catsoop/lib/python3.12/site-packages/websockets/asyncio/server.py", line 284, in __init__ self.loop = asyncio.get_running_loop() ^^^^^^^^^^^^^^^^^^^^^^^^^^ I also tried the above steps but with most recent catsoop. The requirement of websockets==12.0 prevents this issue. A forced upgrade to 16.0 reproduces this error, but there is only select reasons why that may be necessary. An extra note from my own usage: I was able to safely upgrade to 15.0.1 to satisfy additional dependencies for software used in conjunction with catsoop.
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
catsoop/catsoop#108
No description provided.