HAH! Sun

so is there something I can do until this is fixed? Im asking because it is a huge disadvantage not having this hot-readling feature since it is a nice DX....

@KorribanMaster your fork does **not** fix it for me. Cargo.toml: ```rust [dependencies] defmt = "=0.3.8" defmt-rtt = "=0.4.1" static_cell = "=2.1.0" esp-alloc = "=0.5.0" embassy-sync = { version = "=0.6.0"...

tried that too. doesn't work.

so I guess right now `embedded-test` is unusable with embassy. are you guys planning to fix this? @t-moe what is the status of this issue?

ah now I get it: https://github.com/embassy-rs/embassy/blob/c9358e1f1e5d88aa0ad998c44eb2da6be73cf477/embassy-executor/src/lib.rs#L38C1-L38C64 one has to enable the arch feature. in my case (for an esp32c3) I need **arch-riscv32**: ``` embassy-executor = { version = "=0.5.0", features...

considering your comment: > I have forked the repo and set embassy executor to v0.6 only and that solved the issue. Apparently setting a range for allowed external crates comes...

ok investigating further I made it work with version 0.6.0. @KorribanMaster you are funny man. why dont you tell us that your fork is not different from upstream? **ONE HAS...

to summarize: - you need to explicitly specify `arch-riscv32` (or whatever arch you have) feature in `embassy-executor` to get access to the `::Executor` trait in embassy - you need to...

> Oh I guess I never thought someone else would use my fork. However, I always pin everything. I patch to a commit sha as this ensures stability and is...

everything works and Im happy now. you guys decide what you wanna do with this issue. thanks everyone and thank you for this beautiful piece of software.