Skip to content
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

no more watching after first change event #278

Closed
kapouer opened this issue Apr 10, 2015 · 8 comments
Closed

no more watching after first change event #278

kapouer opened this issue Apr 10, 2015 · 8 comments

Comments

@kapouer
Copy link

kapouer commented Apr 10, 2015

Hi,
i'm watching a directory with {depth: 0} as the sole option,
and after first change on a file, it seems to be ignoring further changes.
Using chokidar 1.0.1.

@artem-malko
Copy link

set persistent option to true.
https://github.com/paulmillr/chokidar#persistence

@kapouer
Copy link
Author

kapouer commented Apr 10, 2015

Shouldn't it be the default value ?

@kapouer
Copy link
Author

kapouer commented Apr 10, 2015

It doesn't solve the problem

@es128
Copy link
Contributor

es128 commented Apr 10, 2015

OS? Other options? Text editor?

@kapouer
Copy link
Author

kapouer commented Apr 10, 2015

Umpgh yes sorry, more precisions:

platform debian/jessie, linux 3.16, gnome 3.14.

  • i watch a directory with these options explicitely set:
watcher: chokidar.watch(dir, {depth: 0, persistent: true, atomic: true, followSymlinks: true})
.on('change', changeListener);
  • when i change a normal file twice, everything's all right
  • when i change twice the target of a symlink, the change event is fired twice (or sometimes more times in a row) if i change it twice using vim, but as soon as i change it using gedit no more changes are detected.

Same kind of problem with atomic: false option, in which case i see change and unlink events on regular file, and only one change event on symlink.

@kapouer
Copy link
Author

kapouer commented Apr 10, 2015

With atomic: false on a regular file using gedit:

change /xxx/public/js/.goutputstream-GIOPWX
unlink /xxx/public/js/.goutputstream-GIOPWX
change /xxx/public/js/bindings.js

and using vim

change /xxx/public/js/bindings.js
change /xxx/public/js/.bindings.js.swp
unlink /xxx/public/js/bindings.js~

@es128
Copy link
Contributor

es128 commented Apr 10, 2015

This is the second or third report of gedit causing problems. I still haven't had a chance to study its raw event behavior to augment the atomic adjustments.

In the meantime if you stick to vim or other editors you should be fine.

@es128
Copy link
Contributor

es128 commented Apr 10, 2015

Closing as dupe of #237

@es128 es128 closed this as completed Apr 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants