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
Some sort of async problem, most likely due to the websocket. The only way to reboot the bot is to do a data wipe (second option under 'maintenance' in launcher).
avconv version 11.9-6:11.9-1~deb8u1+rpi1, Copyright (c) 2000-2017 the Libav developers
built on Apr 26 2017 06:57:28 with gcc 4.9.2 (Raspbian 4.9.2-10)
Logging into Discord...
[08/10/2017 14:21] ERROR red <module> 634: Fatal exception, attempting graceful logout
Traceback (most recent call last):
File "red.py", line 614, in <module>
loop.run_until_complete(main(bot))
File "/usr/local/lib/python3.5/asyncio/base_events.py", line 335, in run_until_complete
raise RuntimeError('Event loop stopped before Future completed.')
RuntimeError: Event loop stopped before Future completed.
Task was destroyed but it is pending!
task: <Task pending coro=<Audio.queue_scheduler() running at /home/pi/Test-RedDiscordBot/cogs/audio.py:2235> wait_for=<Future pending cb=[Task._wakeup()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<Audio.disconnect_timer() running at /home/pi/Test-RedDiscordBot/cogs/audio.py:2085> wait_for=<Future pending cb=[Task._wakeup()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<Audio.reload_monitor() running at /home/pi/Test-RedDiscordBot/cogs/audio.py:2239> wait_for=<Future pending cb=[Task._wakeup()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<Audio.cache_scheduler() running at /home/pi/Test-RedDiscordBot/cogs/audio.py:2040> wait_for=<Future pending cb=[Task._wakeup()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<Streams.stream_checker() running at /home/pi/Test-RedDiscordBot/cogs/streams.py:614> wait_for=<Future pending cb=[Task._wakeup()]>>
Red has been terminated. Exit code: 1
Press enter to continue.
The text was updated successfully, but these errors were encountered:
Some sort of async problem, most likely due to the websocket. The only way to reboot the bot is to do a data wipe (second option under 'maintenance' in launcher).
The text was updated successfully, but these errors were encountered: