Proc

As far as I'm aware you will have to handle this on your own. The OS doesn't give you more than these two events and you may have to connect...

What exactly did you mean with ongoing tests ?

Ah ok. Makes sense. We probably need to re-introduce any tests at this points. (And I fear this due to how fragile this all can be and missing any mac...

I'm not sure but I think I've got the same problem, using `5.0.0-pre.1`. I've got foo/ which I watch. I add `foo/A/AA/AA.txt` and can delete `A/` and add it again,...

I switched to 4.0.13 and get the same behavior.

Some deadlocks are fixed now by #210 in the 4.X branch. We'll need some input if that resolves the problems and up-port this to 5.X

Note that since 5.0.0-pre.2 none of the original debouncer code exists any more (and in fact no debouncer for the time being). So this is only v4 related for now....

I can't seem to reproduce this, especially not "Bad file descriptor". Do you have any kind of special file system underlying this ? For example fuse mounts (remote stuff) or...

Could you retry this with the following: cargo.toml dependency entry ```toml notify = "5.0.0-pre.5" ``` main.rs ```rust use notify::{Watcher, RecommendedWatcher, RecursiveMode, Result}; fn main() -> Result { // Automatically select...

> > > I can't seem to reproduce this, especially not "Bad file descriptor". Do you have any kind of special file system underlying this ? For example fuse mounts...