watcher
watcher copied to clipboard
Filesystem watcher. Works anywhere. Simple, efficient and friendly.
Hi @e-dant, I am a bit unsure as to what [`event::effect_type`](https://github.com/e-dant/watcher/blob/release/devel/include/wtr/watcher-/event.hpp#L70) values are set for which filesystem events. This might be due to my lack of experience with filesystem events,...
One of the only filesystems we can't watch is the virtual `/proc` filesystem on Linux. There is a way to create an ebpf program for the kernel to run which...
Recently, on both the `release` and `next` branches, our CodeQL builds have been coming up with this error: https://github.com/e-dant/watcher/actions/runs/6684346814/job/18161503474#step:5:74 We also found this error on a Clang build for Linux...
Every so often, we get an error like this: https://github.com/e-dant/watcher/actions/runs/5920128540/job/16051048104#step:5:33 I tried to address this in https://github.com/e-dant/watcher/commit/38d93a4e09bbcfa2298a3430212690814825b24a by adding a GitHub action to install cmake. Maybe that cmake action isn't...
At some point in the last two weeks, it looks like the GitHub hosted Windows runner changed. For some reason I do not understand, Windows is now failing to execute...
We need performance benchmarks against the other filesystem watchers. I'm thinking: - chokidar - fswatch - watchman - notify-rs We have performance tests, but they're not comparative.
We should investigate boot::asio in these places: - The event loops, which currently use epoll (Linux), iocp (Windows) and dispatch_queue (Darwin). - The user API, which is currently a callback-style...
The messaging syntax (including errors) should be detailed in the readme. Messages come through `event`. The `where` field looks like this: `[s, e]/[sys, self]/[description]` Where `s` means "successful" (such as...