Haptein
commented
5 months ago I am experiencing precisely this bug and I got to the same conclusion after doing some research! I'm getting one of these every one or two days at random, usually on slash commands that take a while to run (after responding the interaction).
Task was destroyed but it is pending!
task: <Task pending name='pycord: on_interaction' coro=<Client._run_event() done, defined at /home/baefloral/.miniconda3/envs/onboardbot/lib/python
3.8/site-packages/discord/client.py:370> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7faece077fd0>()]>>In some cases, the tasks appear to get garbage collected while awaiting one or other time consuming coroutine. This usually results in getting GeneratorExit raised as well.
champymarty
Vondyy
llu13701
Lulalaby
davidhozic
Dorukyum
Summary
When creating tasks with
create_task, PyCord does not save a reference to a task.Reproduction Steps
When creating tasks with
create_task, PyCord does not save a reference to a task, making it a target for the garbage collector, if the task is doing long and complex work.This is well documented by the
asyncio.create_task:Save a reference to the result of this function, to avoid a task disappearing mid-execution. The event loop only keeps weak references to tasks. A task that isn’t referenced elsewhere may get garbage collected at any time, even before it’s done. For reliable “fire-and-forget” background tasks, gather them in a collection
This can eventually result in a "Task was destroyed but it is pending!" error being printed out on screen, because the task was garbage collected. It could also just go though without warning.
Minimal Reproducible Code
Expected Results
The library should save references to task and only remove the reference after the task has been finished.
Actual Results
It doesn't, giving opportunity for the task to be destroyed during execution.
Intents
No intents were passed
System Information
Checklist
Additional Context
No response