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
2023-10-25 17:32:45,185 - asyncio - ERROR - Task was destroyed but it is pending!
task: <Task pending name='Task-8498' coro=<Queue._notify_async_not_empty..f() running at /home/ubuntu/ai-worker/venv/lib/python3.11/site-packages/janus/init.py:238> cb=[set.discard()]>
The text was updated successfully, but these errors were encountered:
Janus creates new tasks in its notification methods to further wake up tasks suspended on the get() and put() methods. You probably are closing the event loop before these tasks have time to complete, which is why you get such flooding. Like @RobertSamoilescu said, you need to close the queue and wait for these tasks to complete. It might be better to explicitly mention this implementation limitation in the README so people know that Janus queues should always be closed correctly.
I get flooded with these when using janus
2023-10-25 17:32:45,185 - asyncio - ERROR - Task was destroyed but it is pending!
task: <Task pending name='Task-8498' coro=<Queue._notify_async_not_empty..f() running at /home/ubuntu/ai-worker/venv/lib/python3.11/site-packages/janus/init.py:238> cb=[set.discard()]>
The text was updated successfully, but these errors were encountered: