The fix for #73 added a new test.
That test is currently failing on macOS.
The underlying filesystem watcher given to us by Apple seems to be dropping events.
Lots of watcher backends will occasionally drop events. The Linux backends (inotify, fanotify) can do that. (Aside: This was one of the things which the experimental eBPF filesystem watcher was meant to address; https://github.com/e-dant/bpf-fs-events).
The test might still be useful to macOS if we slowed the events down a bit, but it was only under those conditions that the bug in #73 appeared. Any accommodations should be platform-dependent.
We don't have much control over when or how the underlying platform watchers drop events. For the Linux watchers, we can at least know if there was a dropped event. That doesn't seem to be the case for macOS.
Fix for #73 was in b8b0d8d
Temporarily disabled tool/test/rename-events-are-associated-events in d6c2dbd
The fix for #73 added a new test.
That test is currently failing on macOS.
The underlying filesystem watcher given to us by Apple seems to be dropping events.
Lots of watcher backends will occasionally drop events. The Linux backends (inotify, fanotify) can do that. (Aside: This was one of the things which the experimental eBPF filesystem watcher was meant to address; https://github.com/e-dant/bpf-fs-events).
The test might still be useful to macOS if we slowed the events down a bit, but it was only under those conditions that the bug in #73 appeared. Any accommodations should be platform-dependent.
We don't have much control over when or how the underlying platform watchers drop events. For the Linux watchers, we can at least know if there was a dropped event. That doesn't seem to be the case for macOS.
Fix for #73 was in b8b0d8d
Temporarily disabled
tool/test/rename-events-are-associated-eventsin d6c2dbd