You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current tests fail on macOS 10.15 because ioutil.TempDir("", "fsexample") creates a file in /var/tmp/... which is a symlink to /private/var/tmp on macOS. I refactored fsevents_test.go in my fork (where I can run test on 10.15 via CircleCI) to show that the failing scenario is the one involving symlinks.
Workaround
The workaround is to use filepath.EvalSymlinks to get the "real" path then use that real path in the construction of your EventStream.
The text was updated successfully, but these errors were encountered:
* Return an error if FSEventStreamStart fails
* Validate the 4096 path limit and error detection
* Add notes for #46 and #48 limitations of macOS
Co-authored-by: Martin Tournoij <[email protected]>
Which version of macOS are you using?
Please describe the issue that occurred.
FSEvents for symlinks on macOS 10.15 aren't being sent or aren't being captured by fsnotify/fsevents.
Are you able to reproduce the issue? Please provide steps to reproduce and a code sample if possible.
fsevents_test.go
modifications to support testing symlink and non-symlink pathsCurrent tests fail on macOS 10.15 because
ioutil.TempDir("", "fsexample")
creates a file in/var/tmp/...
which is a symlink to/private/var/tmp
on macOS. I refactoredfsevents_test.go
in my fork (where I can run test on 10.15 via CircleCI) to show that the failing scenario is the one involving symlinks.Workaround
The workaround is to use
filepath.EvalSymlinks
to get the "real" path then use that real path in the construction of yourEventStream
.The text was updated successfully, but these errors were encountered: