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

Check file listener: new files, symlinks? #14

Open
akerbos opened this issue Jun 25, 2013 · 5 comments
Open

Check file listener: new files, symlinks? #14

akerbos opened this issue Jun 25, 2013 · 5 comments
Labels

Comments

@akerbos
Copy link
Collaborator

akerbos commented Jun 25, 2013

Sometimes, the daemon mode seems to overlook file changes.

There may be problems with

  • symlinked files and
  • (top-level) files created while the daemon is running.

Investigate!

@ghost ghost assigned akerbos Jun 25, 2013
@akerbos
Copy link
Collaborator Author

akerbos commented Nov 20, 2014

listen keeps changing and issues with symlinks have (somewhat) been addressed. See here and here.

It is unclear whether the rather complex listen will be able to do what we want here in an easy and efficient way. One of the lead devs points out that using rb-inotify directly may be an alternative (if only for GNU/Linux). feather_watch may be worth keeping an eye on.

What are other alternatives?

@e2
Copy link

e2 commented Nov 27, 2014

It's a tough issue, and you'll probably get the most clarity from these: guard/listen#280 and guard/listen#279

@akerbos
Copy link
Collaborator Author

akerbos commented Nov 27, 2014

Thanks, I'll keep watching! Chances are that by the time I actually get around to working on this again, you'll have come up with something that works for me. :)

@e2
Copy link

e2 commented Nov 27, 2014

Also, as far as I know changing the directory structure while Listen is running is undefined on Linux.

@reitzig
Copy link
Owner

reitzig commented Feb 26, 2016

Seems not to be resolved in Listen yet.

Should we resolve all symlinks before passing files to Listen?

@reitzig reitzig removed this from the Release 1.0 milestone Feb 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants