Kaleb Barrett

@jwprice100 Actually... I see your point. With the implementation of `select` I gave you it sets an `Event` and then continues. Another task could finish before the `Event` is handled...

> Uh oh, the API of select doesn't support this This is not possible if you don't implement `select` with `asyncio.wait` like you have done. As soon as one task...

> won't they both finish before wait is resumed? Depends... If you are `await`ing a Task and it finishes, execution jumps to the scheduler (due to the `yield self` in...

There are issues with `asyncio.wait`. As soon as you segregate the futures into two different lists you obliterate any information matching the inputs to the outputs. Such a function should...

No that is a different issue. This issue only *potentially* affects logs from C code. I would open a separate issue for that.

Likely changed in https://github.com/cocotb/cocotb/pull/565. The implementation of external used to be implemented entirely within the the decorator; there was no scheduler interaction. You can probably copy/paste and see if this...

If that is the intended use case (IMO that sounds like a problem exactly 1/2 of a person has ever had), then the documentation needs to be clarified. `external`/`function` are...

The patch never really worked. Nothing I tried really worked either. If you want to provide a solution, I would start from scratch. I think a better solution than asking...

> One potential issue is that currently github action does not have arm runners, but it's still possible to have them trough [qemu + docker ](https://github.com/dbhi/qus). Looks promising. Can you...

Are you using the most recent version of cocotb? We have struggled with the same issue using Questa for some time, but I have not seen it recently.