In the asyncio example in flags2_asyncio.py there is a bug when a call to a coroutine in the loop fails and the next one has success, the error variable doesn't get reset and it still thinks it got an error, and updates the counter[status] with the wrong value
In the
asyncio
example inflags2_asyncio.py
there is a bug when a call to a coroutine in the loop fails and the next one has success, theerror
variable doesn't get reset and it still thinks it got an error, and updates thecounter[status]
with the wrong value