extmod/uasyncio Event.set() not safe in ISR
If you call Event.set() in an ISR, you could end up losing all tasks that were awaiting the event (if the ISR is executed while uasyncio is sorting tasks on the queue e.g.).
I made a testscript a while ago to demonstrate this: https://gist.github.com/kevinkk525/5b89395604da3df3be7a015abcba04fa
extmod/uasyncio: Loop exits if only Tasks awaiting Events are added
If only Tasks are added to the Loop that are waiting for an Event to be set (or a Lock to be acquired but that makes no sense at all), the loop exits because those Tasks get removed from the main queue and put onto the waiting queue of the Event.
Use-case: Event is waiting to be set from an ISR. Will probably only ever be used without other Tasks running in minimal test-cases but would then be a problematic bug.
Expected behaviour: Loop continues to run. This needs #5795 (Events from ISR). Otherwise this problem will of course never occur.
>>> import uasyncio as asyncio
>>> ev=asyncio.Event()
>>> async def wait():
... print("started waiting")
... await ev.wait()
... print("got event")
...
...
...
>>> asyncio.run(wait())
started waiting
>>>