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
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This appears to be due to the linux file system
inotify
event being generated inside the Dinghy VM changing to a:modify
event, which theListen
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: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:7The text was updated successfully, but these errors were encountered: