[Bug] Radom BadNameSpaceError when starting a node

[hcadavid]

Describe the bug
When starting a node (v6 node start), sometimes it crashes while trying to share its configuration with the server:

2024-06-14 12:32:58 - node           - DEBUG    - Sharing node configuration: {'encryption': True, 'allowed_algorithms': 'all', 'database_labels': ['default'], 'database_types': {'db_type_default': 'csv'}, 'database_columns': {'columns_default': ['Name', 'Age', 'Location']}}
Exception in thread Thread-6 (_handle_eio_message):
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.10/threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.10/site-packages/socketio/client.py", line 705, in _handle_eio_message
    self._handle_event(pkt.namespace, pkt.id, pkt.data)
  File "/usr/local/lib/python3.10/site-packages/socketio/client.py", line 581, in _handle_event
    r = self._trigger_event(data[0], namespace, *data[1:])
  File "/usr/local/lib/python3.10/site-packages/socketio/client.py", line 636, in _trigger_event
    return self.namespace_handlers[namespace].trigger_event(
  File "/usr/local/lib/python3.10/site-packages/socketio/namespace.py", line 18, in trigger_event
    return getattr(self, handler_name)(*args)
  File "/vantage6/vantage6-node/vantage6/node/socket.py", line 46, in on_sync
    self.node_worker_ref.share_node_details()
  File "/vantage6/vantage6-node/vantage6/node/__init__.py", line 1096, in share_node_details
    self.socketIO.emit("node_info_update", config_to_share, namespace="/tasks")
  File "/usr/local/lib/python3.10/site-packages/socketio/client.py", line 393, in emit
    raise exceptions.BadNamespaceError(
socketio.exceptions.BadNamespaceError: /tasks is not a connected namespace.
2024-06-14 12:32:58 - socket         - INFO     - Node <collab-One - orgA> joined room <collaboration_1>

Despite the error, the node keeps running (in the UI it is shown as 'active'/green), and the problem is noticed only when you try to create a task (e.g., from the UI), as there are no databases to choose from.

This happens randomly, but happens almost 100% of the time when using nodes running within a SURF-RC Workspace (I still don't understand why). When running the node within the same v6-server's workspace, it happens around 50% of the time.

In my case, the v6-server is running through docker-compose, with an NGINX reverse proxy as an entry point for the API and the web-based UI:

server {
	listen 80 default_server;
	listen [::]:80 default_server;
	return 301 https://$host$request_uri;
}

server {
	# SSL configuration
	#
	listen 443 ssl default_server;
	listen [::]:443 ssl default_server;

	server_name ....;
	ssl_certificate ...;
	ssl_certificate_key ....;

        location /api {
          include proxy_params;
          #proxy_set_header Host $host;
          #proxy_set_header X-Real-IP $remote_addr;
          proxy_pass http://localhost:5000/api;
        }

        location / {
          #include proxy_params;
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_pass http://localhost:8080/;


          sub_filter 'src="/' 'src="/ui/';
          sub_filter_once on;
          sub_filter_types text/html text/css application/javascript text/javascript;


	}

    	# Allow the websocket traffic
    	location /socket.io {
          include proxy_params;
          proxy_http_version 1.1;
          proxy_buffering off;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "Upgrade";
          proxy_pass http://127.0.0.1:5000/socket.io;
	}

}