New submission from Sheng Zhong :
An exception is raised and propagates up the call stack without being consumed
until the asyncio/events.py:_run function. The exception seemingly doesn't get
consumed according to my breakpoint (quite strange and a part of my confusion)
but the task doe
Sheng Zhong added the comment:
Sorry I'm having trouble extracting a bug-producing portion of the code but I
can describe the different components, what I think the problem was, and how I
resolved it.
There is one main coroutine (aka handler) responsible for handling the log
New submission from Sheng Zhong :
As far as I know, there is no mechanism for aborting a created coroutine
instance before it's executed with an await (directly or indirectly). I have a
function which takes in coroutine instances and conditionally creates a task
for them that I track so
