bug: websockets.exceptions.ConnectionClosedError: no close frame received or sent

[mikeshultz]

What went wrong?

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/silverback_platform/runner.py", line 238, in _process_events
    async for raw_event in self.subscriptions.get_subscription_data(sub_id):
  File "/usr/local/lib/python3.11/site-packages/silverback/subscriptions.py", line 123, in get_subscription_data
    await self.__anext__()
  File "/usr/local/lib/python3.11/site-packages/silverback/subscriptions.py", line 49, in __anext__
    message = await self.connection.recv()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/websockets/legacy/protocol.py", line 568, in recv
    await self.ensure_open()
  File "/usr/local/lib/python3.11/site-packages/websockets/legacy/protocol.py", line 939, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: no close frame received or sent

How can it be fixed?

Would be good to have better error handling and recovery for Websockets. For long running processes, these errors are inevitable.

[linear]

SBK-434 bug: websockets.exceptions.ConnectionClosedError: no close frame received or sent

[fubuloubu]

p.s. was trying to tackle this in #78 if you want to take the torch on that