Flow: Flow server fails silently when inotify limit is reached
When the limit of inotify watches is reached, Flow server obviously does not recheck source files when they have changed. It will emit the same diagnostics every time, despite source file changes. It took me a long time to figure out this was due to the inotify limit being reached, though, because Flow server silently fails. I think it should tell me when it reaches the inotify limit, instead of failing silently.
I use Flow 0.22.1 on Gentoo Linux 4.1.12.
rightfold
All 4 comments
Yikes. Thanks for letting us know.
samwgoldman
on 5 Mar 2016
This bug has just bitten my teammate (who also was new to Flow, so this was doubly inconvenient!)
He is on Ubuntu, and we solved it by upping the inotify limit from 8192 to 65536:
sudo sysctl fs.inotify.max_user_watches=65536
Not failing silently would be a good thing, needless to say :)
tempname11
on 24 Jul 2017
@tempname11 that solves the problem for Xubuntu 18.04 w/ flow-bin 0.78.0. Thanks!
uladkasach
on 7 Aug 2018
I had the same issue and took a while to realise what was going wrong. Thanks to tail it warned me about the inotify limit being reached !!
manjunath-satyamurthy
on 3 Sep 2018
Related issues
funtaps
路
3Comments
iamchenxin
路
3Comments
davidpelaez
路
3Comments
pelotom
路
3Comments
marcelbeumer
路
3Comments
Most helpful comment
This bug has just bitten my teammate (who also was new to Flow, so this was doubly inconvenient!)
He is on Ubuntu, and we solved it by upping the inotify limit from 8192 to 65536:
sudo sysctl fs.inotify.max_user_watches=65536Not failing silently would be a good thing, needless to say :)