-
-
Notifications
You must be signed in to change notification settings - Fork 899
Replies: 1 comment · 8 replies
-
I'm sorry but I need more details. There are 5 emits in the code that you included in your question. Which one isn't working? And also, can you please enable detailed Socket.IO logs in your server and provide the logs for the emit(s) that don't work? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, sorry for the inconvience and this large of a log |
Beta Was this translation helpful? Give feedback.
All reactions
-
Your logs shows that there are 61 clients in this room. You have included 12 emits in this log section, and each was sent to the 61 members. What problem are we looking for here specifically? |
Beta Was this translation helpful? Give feedback.
All reactions
-
The issue is that only 1 user is connected to the room but the logs are showing way more users in the room, |
Beta Was this translation helpful? Give feedback.
All reactions
-
The code that you shared does not show any users joining any rooms. You also did not include the log portion in which your user connected. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, Currently I am unable to re prodcue the issue. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
this is my code for the flask app and there are 2 redis queus for emiting the data but in them there is a issue that many times data was not recieved in the frontend.
So dig deeper and tried to find the reason, the reason was that the room that was created, manytimes it is empty even though the user is connected so i am unable to get the reason behind it.
So if anyone can help then it would be very helpful.
Here sid === room_name
Beta Was this translation helpful? Give feedback.
All reactions