socketio.exceptions.BadNamespaceError: / is not a connected namespace. #1589
Replies: 5 comments 1 reply
-
Yes, this issue is known and is explained here: miguelgrinberg/python-socketio#634. The master branch of python-socketio has a fix, but it hasn't been released yet. Feel free to install from git if you want to try out the fix, or else you can also change your application as suggested in the issue linked. |
Beta Was this translation helpful? Give feedback.
-
Great, @miguelgrinberg ! Thanks. |
Beta Was this translation helpful? Give feedback.
-
Hi @miguelgrinberg , I am using the 5.0.2.dev0 version now. But, the problem still persists. I am using a sio.sleep(1) after the connect as well. Any insights after this? |
Beta Was this translation helpful? Give feedback.
-
@mishkat-ucr the fix is not in this repo, it's in python-socketio. That's the one you need to install from git. |
Beta Was this translation helpful? Give feedback.
-
face connecting error
I am able to connect to the server using java socket client with version:
It seems that there is some issue on the python socket client side on the lastest version 5.3.x above. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying out one use case here, which is: send over some data in batches to the client. I will initiate an event from the client, in which server will respond with another event which will send the next batch. In a nutshell, I'm trying to achieve some sort of synchronicity in an asynchronous event based mechanism.
Here is the gist of my client code:
Here is the gist of my server code:
However, I am getting a
socketio.exceptions.BadNamespaceError: / is not a connected namespace.
error. Any idea why?Beta Was this translation helpful? Give feedback.
All reactions