You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running AutoShardedBot (which Botto uses) then exiting on Windows, you may get an exception such as follows:
Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x00000181F2917EE0>
Traceback (most recent call last):
File "c:\users\music\appdata\local\programs\python\python38\Lib\asyncio\proactor_events.py", line 116, in __del__
self.close()
File "c:\users\music\appdata\local\programs\python\python38\Lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "c:\users\music\appdata\local\programs\python\python38\Lib\asyncio\base_events.py", line 715, in call_soon
self._check_closed()
File "c:\users\music\appdata\local\programs\python\python38\Lib\asyncio\base_events.py", line 508, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
This is an issue with aiohttp, as seen in aio-libs/aiohttp#4324.
This error does not affect Botto in anyway, just that it only creates a dissatisfying output on exiting the process. It can be safely ignored.
Nonetheless, you should opt to host bots on a Unix server instead. You can test Botto using Docker when developing on a Windows machine, then host it in a Docker container or push it to your production server.
The text was updated successfully, but these errors were encountered:
When running
AutoShardedBot
(which Botto uses) then exiting on Windows, you may get an exception such as follows:This is an issue with aiohttp, as seen in aio-libs/aiohttp#4324.
This error does not affect Botto in anyway, just that it only creates a dissatisfying output on exiting the process. It can be safely ignored.
Nonetheless, you should opt to host bots on a Unix server instead. You can test Botto using Docker when developing on a Windows machine, then host it in a Docker container or push it to your production server.
The text was updated successfully, but these errors were encountered: