Open samayala22 opened 2 years ago
What code are you using to reproduce this? If I'm running the code in the example
directory it seems to work as intended.
Are you using the environment from the Pipenv
file locked to the exact versions of socketio
?
Hey, sorry for the late response, was busy all week.
Yeah when using socketio version 5.4.0 I don't get the error anymore. However, another breaking error appeared.
Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x00000291E69F61F0>
Traceback (most recent call last):
File "C:\Python\Python39\lib\asyncio\proactor_events.py", line 116, in __del__
self.close()
File "C:\Python\Python39\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "C:\Python\Python39\lib\asyncio\base_events.py", line 746, in call_soon
self._check_closed()
File "C:\Python\Python39\lib\asyncio\base_events.py", line 510, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000291E750DA00>
I'll try to find the event that triggers it.
No worries!
Right, I see that I've configured the Pipefile
with a minimum version but no max version. I should lock that to a version that runs for me.
Double checking again, is this reproducible with the code in the example
directory?
Feel free to file a PR if you figure out what the issue is!
Hey, having a hard time understanding a way to fix this "Invalid Namespace" response parsing issue.
The extra debug info was obtained using
sio = socketio.AsyncClient(logger=True, engineio_logger=True)
in the scorebot file.