Number of participants is wrong when run on another process

[TelegramXPlus]

I have a socket.io instance running alongside fastapi and uvicorn, which uses the AsyncRedisManager.

I do also have an arq worker that uses another socket.io instance again with the AsyncRedisManager. The issue is that when I try to get the participants using sio.manager.get_participants(...) I get back 0 users from the arq worker, while the uvicorn worker doesn't give any issue. And I am running the arq worker before the uvicorn worker.

Looking at the documentation it seems that the manager is automatically connected (considering that when I was using the wrong env it was giving errors).

Is there something I can do to fix that, or I just should not try to get participants from the arq worker. And do this also affect multiple workers for uvicorn?

[TelegramXPlus]

I just checked and there is another questions that ask the same

[miguelgrinberg]

I think this needs to be clarified better in the documentation. The get_participants() method returns the clients that are connected to the server process in which you call the method. In an external worker process there are no connected clients, so you will always get 0. On multiple uvicorn workers, each worker will give you the list of clients that it knows about.

This package does not maintain a unified list of connected clients. If your application has access to a database, for example, maintaining a complete list of clients should be possible.

[TelegramXPlus]

Indeed, that is why I tried to use redis directly to get the sids in a room, however it seems like the redis manager is not saving anything? When looking at the CLI/Redis Insight I do not have any keys, and when using (await sio.manager.redis.keys("*")) I get an empty list? However I am using the correct db (default one), and when using arq I don't have these problems as I can see the keys on Redis. Is it because Pub/Sub is only for emetting events and not storing info such as?

In that case I suppose I should handle my own redis participants using I.E. await sio.manager.redis.sadd(f"socketio:rooms:/:{room}", sid)?

Nonetheless my pyproject.toml contains:

python-socketio[asyncio-client]>=5.13.0
redis>=5.2.1

[miguelgrinberg]

No, you are mistaken. This package does not use a database. It uses a message queue. If you use Redis, then the messaging is implemented through the pub/sub mechanism. Many other message queues are supported as well, but this feature is for message passing, not for storage.