thread '<unnamed>' panicked at 'internal error: entered unreachable code', ../src/libstd/sync/mpsc/mod.rs:565 about cargo-watch HOT 7 CLOSED

Can you just use notify = "^2.1" as in current source, that should get the latest with the current Cargo.lock, your revision is technically same code and thus useless.

from cargo-watch.

Can you also provide the exact steps you use to make this segfault?

from cargo-watch.

I started by:

1. git clone ....
2. cargo build --release
3. cp build/[...]/cargo-watch /usr/local/bin
4. In project folder "cargo watch"
   --> On file change I get the segfault on MacOs (but works in Ubuntu)

I searched in the net and found above issues:
5) changed Cargo.toml to ensure notify contains the patch
notify = { git = "https://github.com/passcod/rsnotify.git", rev = "5a48333dde58a01f68c1e6" }
5) cargo update
6) cargo build --release
7) cp build/[...]/ /usr/local/bin
8) In project folder "cargo watch"
--> On file change still segfault. :-(

I also tried with notify master, but no difference. I have in also deleted old versions of cargo-watch /usr/local/bin to make sure no old version is remaining, also I tried "cargo clean" in between.

Version: macos el capitan
Rustc: 1.4

I'm novice to rust, sorry if I made something wrong.

from cargo-watch.

Moving discussion to notify-rs/notify#33 as this seems to be an upstream issue.

from cargo-watch.

@fritzsche can you verify that it is fixed, when building against:

notify = { git = "https://github.com/octplane/rsnotify.git", rev="5a9d08d94665b3d53f78f4a9aab2d9fa8e0d70f8" }

Thank you.

from cargo-watch.

This commit fixed the issue for me.

from cargo-watch.

Thank you @fritzsche . I am awaiting for peer reviews regarding the patch. I should land in rsnotify quickly. Thank you again for your report and validation!

from cargo-watch.