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

The Ruby Guard gem is broken on Dinghy 4.6.5 #279

Open
ms-ati opened this issue Jul 11, 2018 · 1 comment
Open

The Ruby Guard gem is broken on Dinghy 4.6.5 #279

ms-ati opened this issue Jul 11, 2018 · 1 comment

Comments

@ms-ati
Copy link

ms-ati commented Jul 11, 2018

This appears to be due to the linux file system inotify event being generated inside the Dinghy VM changing to a :modify event, which the Listen gem does not, by default, create a watch for.

Please see Listen gem issue 450 for more information and to track that.


As a workaround, adding the following line to your Guardfile appears to work:

Listen::Adapter::Linux::DEFAULTS[:events] << :modify

The underlying issue in the Listen gem appears to be the absence of :modify from the above constant which is defined in listen/adapter/linux.rb:7

@codekitchen
Copy link
Owner

Oh hm, I didn't realize that switching to gtouch would change the event from ATTRIB to MODIFY but I've just tested to verify that is the case. That's going to fix things for some people and break things for others (like here), another related ticket is codekitchen/fsevents_to_vm#7

I wonder if there's a reasonable way to generate both ATTRIB and MODIFY events. One solution might be to call touch and then gtouch in sequence, but I worry about race conditions there.

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
@codekitchen @ms-ati and others