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
file watch is not reliable on linux #1058
Labels
Comments
jennifer-shehane
added
the
stage: needs information
Not enough info to reproduce the issue
label
Dec 12, 2017
You may want to check out this thread, because linux can run into problems with the inotify limit of the kernel: https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached |
@acthp Any update on this from your end? |
Closing as stale. No response in over a year. Please comment if you are still experiencing this issue. |
jennifer-shehane
removed
the
stage: needs information
Not enough info to reproduce the issue
label
Mar 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a Feature or Bug?
bug
Current behavior:
UI stops responding to file updates
Desired behavior:
UI consistently responds to file updates
How to reproduce:
Unclear. It happens very regularly, like every 5 minutes or so, during regular use. I sometimes convince myself that it happens after an error, like a syntax error in the spec file, but I've never been able to invoke the bug by introducing errors.
Once this state occurs, it can only be cleared by killing the cypress process and restarting. Hitting 'stop' on the UI, and restarting the spec file doesn't help. Neither does reloading the browser tab. It will never pick up changes to the spec file until the cypress process is killed and restarted.
Also, to be clear, this never happens on OSX.
The text was updated successfully, but these errors were encountered: