failed to sync created files from Linux host due to inotify bug

[hoatle]

egor.k [2:05 AM] 
@hoatle hello again
There is a bug I think, when I create a migration file (I usually duplicate the last one) and then modify it, it doesn't synchronize with virtual machine.
Like this:
1. copy the last migration (with a new folder name of course) - sync works
2. make changes in a new migration's `up.sql` file - sync doesn't work anymore for this file

`vagrant reload` helps, but maybe there is a known way to force all files sync manually or something like this, that doesn't involve rebuild?
I don't create migrations often so it's no very important (edited)

hoatle [7:32 AM] 
thank you @egor.k, sync should work, @phuong please help checking on this

phuong [8:52 AM] 
ok

after triaging, @phuonglm found out that it was a inotify bug and @phuonglm will continue to handle this.

Hopefully this can be fixed by v0.5.0-c1

[hoatle]

phuonglm [10:37 AM] 
bug found

[10:37] 
https://github.com/guard/rb-inotify/blob/master/lib/rb-inotify/notifier.rb#L208

[10:37] 
bug only on Linux

[10:38] 
because inotify on linux did not support recursive

[10:38] 
and the lib used recursive to add all sub directories into the watch list

[10:39]
and the new sub directories was not added to the watch list => bug

[hoatle]

hoatle [6:50 PM] 
@egor.k I guess the workaround is: stop the rsync watch and then `$ vagrant gatling-rsync-auto` instead of `$ vagrant reload`, @phuong could you confirm this workaround?

phuong [6:50 PM] 
yes, that workaround worked

hoatle [6:51 PM] 
@egor.k please use that workaround until we fix it, thank you.

[hoatle]

move this issue out of v0.5.0-c1 release, it requires more workload than expected.

[phuonglm]

related issues guard/rb-inotify#75

[hoatle]

@duc4nh maybe you could help on this?

[hoatle]

this should be the bug fix from extension, so close.

[hoatle]

This issue was moved to teracyhq-incubator/teracy-dev-essential#28