Will

> I created a minimal reproducer here: [https://github.com/AlliBalliBaba/watcher-debug](https://github.com/AlliBalliBaba/watcher-debug) The watcher here is being closed before it has a chance to finish opening all the resources it needs. The thread running...

With some extra logging, we can trace what's happening: ``` close/1/1727620570393 closing watcher close/1/1727620570393 releasing semaphore close/1/1727620570393 waiting for watcher open/1/1727620570393 watching /go/src/app open/1/1727620570393 e/self/live@/go/src/app event: path name: e/self/live@/go/src/app path...

However, I'm not sure this fully addresses the issue. While, in this example, the issue could be solved by waiting for that self/live message (with the special "watcher" path type),...

Re: > I guess I'm fine with the current behavior then. It could maybe be documented somewhere that wtr_watcher_close will return false (but still stop the watcher) if the watcher...

Some downsides to e-dant/watcher that might affect you here - It *only* supports recursive watches. We do this because the performance impact is almost nothing (we test to be sure...

> The only thing that worries me are the static builds since I have no idea how to make them work with these external libraries. Checkout this C shared (or...

Would it be useful to you if I added CI in watcher for arm (64/a53/72, and 32/v7), x86/64, glibc and musl, for kernels > v5 or v6 ish on Linux?...

> While it would be nice to have a download, I don't think it's necessary since we're running the pipelines here for all the supported environments anyways. I added a...

> Does the library have to be linked or complied in a very specific way? I don't know if there's any magic above the C/++ code that's needed, but at...

It is somewhat more difficult for me to track down and resolve Windows issues, since I don't have a Windows development environment (outside of GitHub actions runners, I guess). So,...