Closed Dragoncraft89 closed 3 years ago
@Dragoncraft89 that's pretty weird, I would expect it to work. I'll take a look into it this weekend (or earlier if I have time), and try and get a patch released.
@Dragoncraft89 I was unable to reproduce "Invalid Instruction", it works fine using future's block_on()
on my machine (running Fedora Workstation Linux). I had to reduce the amount of unsafe code depended on for the new version 0.9 that I just released, would you mind testing again with wavy 0.9 and see if the undefined behavior is still there?
Can confirm that 0.9 works.
Thx a lot. I'll be closing this then
Describe the bug Running wavy in another async executor, such as the
futures
crate, results in anInvalid Instruction
. I had a quick look into thepasts
crate and what itsblock_on
does, but I haven't figured out why this happens. It looks like undefined behaviour to me.To Reproduce Here's a modified version of
monitor.rs
, that I could trigger the bug with:Expected behavior Not an "invalid instruction" :wink:
I expected it either to work the same as with the
pasts
crate or give me some form of compile time error.Desktop (please complete the following information):