search

shama / gaze

:crystal_ball: A globbing fs.watch wrapper built from the best parts of other fine watch libs.
MIT License
1.16k stars 167 forks source link

Repeated events over Windows network share #196

Open pdeffendol opened 9 years ago

pdeffendol commented 9 years ago

This problem has also been reported as gulpjs/gulp#1116 but I suspect it's not directly Gulp-related.

I'm watching for file change events (via Gulp.watch) on Windows, with the files located on a mounted Windows network share. The events are fired almost constantly, and repeatedly for each watched file, with no changes being made to the files being watched. See the linked issue above for a more lengthy example.

dmacdnld commented 9 years ago

I am experiencing this as well. I suspect this is an issue with Parallels because a coworker of mine using VM Fusion isn't running into this issue and neither are my other coworkers who aren't using any VM.

davebrong commented 9 years ago

I'm experiencing a similar issue, but my environment might differ slightly. I run the website/gulp inside of a virtual machine, and my host uses a network share to run the code editor. When I save a file, the gulp.watch inside the VM fires, but I noticed that the gulp.dest() function doesn't actually do anything --- any modified files in the stream get placed into the source directory -- which in this case is my ./scss directory, which again triggers gulp.watch (src = ./scss/*/)

I can fix it by only watching for the ./scss/*.scss files, but the gulp.dest still places processed files inside of that directory.

I'm not sure if the bug is with gulp.watch, gulp,dest or gulp-sass -- or none of the above and with nodejs itself on how a network file save triggers differently.

(grunt works just fine)

pdeffendol commented 9 years ago

See the Parallels Forum at https://forum.parallels.com/threads/grunt-gulp-watch-from-windows-guest-to-mounted-mac-drive.328830/#post-776203 for a more official response.