-
Notifications
You must be signed in to change notification settings - Fork 136
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
Polling instead of inotify #40
Comments
I'm having the same issue on my Vagrant environment. I've found an issue opened for fsnotify fsnotify/fsnotify#9. |
If we implemented polling, how would we detect that the normal notification method or the platform doesn't work and that we should poll instead? |
I can confirm the same issue when using Docker for Windows.
I think it should be by ways of configuration instead of automatic detection. Similar to https://webpack.js.org/configuration/dev-server/#devserverwatchoptions-
|
This issue has pained me for a long time. I tried the polling method but it gets slow when the project is big. I finally decided to write my own tool to overcome this problem. It has a similar design to reflex. Hope this will help you guys: https://github.com/AgentCosmic/xnotify |
I am currently using reflex to recompile go application when something changes. Unfortunately I noticed reflex is not working properly when inside a VM with filesystems like vboxsf. Is there any chance that reflex will support somethink like force-polling or polling as a fallback?
The text was updated successfully, but these errors were encountered: