Ensure proper closing of websockets

[frode-aarstad]

When running everest with debugging the following exception is thrown when closing down:

2025-03-20 11:32:17,705 websockets.client DEBUG: = connection is CLOSED
2025-03-20 11:32:17,718 everest.detached DEBUG: Traceback (most recent call last):
  File "/private/faar/bleeding/root/lib64/python3.11/site-packages/everest/detached/__init__.py", line 298, in start_monitor
    message = websocket.recv(timeout=1.0)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/prog/res/komodo/bleeding-20250320-0207-py311-rhel8/root/lib64/python3.11/site-packages/websockets/sync/connection.py", line 336, in recv
    raise self.protocol.close_exc from self.recv_exc
websockets.exceptions.ConnectionClosedError: no close frame received or sent

2025-03-20 11:32:17,718 everest.bin.everest_script DEBUG: Everest experiment finished

Ideally we should close down the socket gracefully

[DanSava]

Is there a special way to trigger this behaviour? I tried to do it using everest run config_minimal.yml --debug and could not even when running it multiple times.

[frode-aarstad]

Is there a special way to trigger this behaviour? I tried to do it using everest run config_minimal.yml --debug and could not even when running it multiple times.

There used to be an exception at the end when running with --debug stating that the websocket was not closed. I am not able to reproduce it either. So we can just close it