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
I'm currently developing with Buffalo framework and running it inside container using dev mode with buffalo dev command.
And seems that buffalo is using fsnotify for listening filesystem events and when using mutagen for syncing sources between host and container file change/modification is not triggered inside container and thus doesn't trigger the build on buffalo dev mode.
Syncing seem to work perfectly fine, but i'm missing some filesystem events.
The text was updated successfully, but these errors were encountered:
Thanks for the report. I suspect this is the same issue that #158 is addressing (namely that Mutagen swaps files in with an atomic rename operation that some file watchers don't pick up on). The solution here is probably going to be the touch operations described in #158. See the Spectrum chat for a bit more background information.
If that doesn't sound like the problem you're having, please let me know. I'll use this as the tracking issue for now and update it once I ship out a fix. I can't give an exact date at the moment, but there's a backlog of issues that I'd like to get through by the end of the coming weekend.
xenoscopic
changed the title
Some filesystem events not triggered inside Docker environment
Atomic renames don't trigger all filewatchers
Oct 21, 2019
I'm currently developing with Buffalo framework and running it inside container using
dev
mode withbuffalo dev
command.And seems that buffalo is using fsnotify for listening filesystem events and when using mutagen for syncing sources between host and container file change/modification is not triggered inside container and thus doesn't trigger the build on
buffalo dev
mode.Syncing seem to work perfectly fine, but i'm missing some filesystem events.
The text was updated successfully, but these errors were encountered: