"Task was destroyed but it is pending!"

[mhchia]

We get this kind of exceptions in many places in the tests, actually too many. It is because tasks are not tear down properly. We should revisit places where create new tasks and add proper exception handling logics.

RuntimeError: Event loop is closed
Task was destroyed but it is pending!
task: <Task pending coro=<Queue.get() done, defined at /Users/mhchia/.pyenv/versions/3.7-dev/lib/python3.7/asyncio/queues.py:150> wait_for=<Future cancelled>>

[moshemalawach]

Also getting it when I use the timeout feature of asyncio, like this:

await asyncio.wait_for(host.new_stream(peer_id, [PROTOCOL_ID]), connect_timeout)

[ShadowJonathan]

We're planning to switch to trio (#174) or anyio (#383), the latter of which implements a pytest plugin, maybe it's a good time to revisit this issue when or while the change is underway?