We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See issue on the rails repo.
The text was updated successfully, but these errors were encountered:
This should be reported on https://github.com/thibaudgg/rb-fsevent
That's because Rails Spring listener creates the forks and rb-fsevent creates the processes.
Listen can't really do much here to fix this (as far as I know), unless the watchers aren't being closed properly.
There's also a quite recent commit like this: guard/rb-fsevent@c9deae0
So you may want to try different rb-fsevent versions (including earlier ones) - or even build a gem from the rb-fsevent master branch.
Also, Listen (or rb-fsevent) may be crashing - and not closing the processes for some reason.
You may want to try running Listen in debug mode with an environment variable like: export LISTEN_GEM_DEBUGGING=1 or export LISTEN_GEM_DEBUGGING=2.
export LISTEN_GEM_DEBUGGING=1
export LISTEN_GEM_DEBUGGING=2
You might want to check if the above code in rb-fsevent (for killing the process and closing the pipe) if it actually works.
Sorry, something went wrong.
@e2 don't really want to test it out, as I found a workaround, and I don't want to have to reboot.
No branches or pull requests
See issue on the rails repo.
The text was updated successfully, but these errors were encountered: