Task was destroyed but it is pending!

[euri10]

is there a way to avoid those warnings on my tests ?

Task was destroyed but it is pending!
task: <Task pending name='Task-4' coro=<AsyncWebSocketSession._background_receive() done, defined at /home/lotso/.cache/pypoetry/virtualenvs/lemongpt-jx0mSZeq-py3.11/lib/python3.11/site-packages/httpx_ws/_api.py:915> wait_for=<Future finished result=None>>
Task was destroyed but it is pending!
task: <Task pending name='Task-5' coro=<AsyncWebSocketSession._background_keepalive_ping() done, defined at /home/lotso/.cache/pypoetry/virtualenvs/lemongpt-jx0mSZeq-py3.11/lib/python3.11/site-packages/httpx_ws/_api.py:952> wait_for=<Future pending cb=[Task.task_wakeup()]>>
Task was destroyed but it is pending!
task: <Task pending name='Task-9' coro=<sleep() done, defined at /home/lotso/.asdf/installs/python/3.11.2/lib/python3.11/asyncio/tasks.py:627> wait_for=<Future pending cb=[Task.task_wakeup()]>>

[frankie567]

Hmm 🤔

In your test code, do you make sure the .close() method is called before ending the test session? Either implicitly by properly ending the context manager, or explicitly by calling .close()?

[euri10]

a await asyncio.sleep(0.1) (0.0 doesnt work, in fact any delay above 0.0 seems ok) works if placed either at same level of the first context manager or second one, it still warns me with the sleep inside at assert level inside the 2 contexts managers.

[euri10]

seems like pytest-dev/pytest-asyncio#309 would solve it

[frankie567]

Oh, interesting! Thanks for the investigation @euri10 :) I'll watch this!

[euri10]

finally found the time and I can confirm the PR above fixes the warnings.
I also quickly watched over anyio marker implementation and didn't see an equivalent "cleaning" process though.

[frankie567]

Thanks 🙏