-
-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renamed events are not properly combined on macOS 11 #723
Comments
Never mind, this issue is bogus. For some reason, the |
Those event IDs which Python receives are definitely strange. They are not monotonically increasing and often repeat themselves. Those surely cannot be the event IDs as documented in https://developer.apple.com/documentation/coreservices/fseventstreameventid?language=objc. @CCP-Aporia, do you have any idea what may be going on here? |
Ok, I found the issue. You have been passing event flags instead of IDs: watchdog/src/watchdog_fsevents.c Lines 302 to 304 in d0bb7b8
|
I'm having trouble handling |
No, that is issue #721 which has already been fixed in the master branch. |
On macOS 11 and possibly previous releases, renamed events are not properly combined to a single event but are reported as separate deleted and created events instead.
The FSEventStream on macOS always reports two renamed events: one at the old path and one at the new path. Watchdog tries to combine them intelligently and relies on an undocumented observation that the event IDs of those two events will only differ by one:
watchdog/src/watchdog/observers/fsevents.py
Lines 88 to 96 in d0bb7b8
However, macOS 11, the two events will have equal event IDs. This may be the result of changes to APFS and atomic file moves.
The text was updated successfully, but these errors were encountered: