Even when spring is disabled, this gem still tries to watch files
RobinClowers opened this issue ยท 5 comments
In my CI env, I export DISABLE_SPRING=1
, but then I get errors about increasing the inotify limits anyway. It seems like this gem shouldn't try to do anything if spring is disabled.
I can confirm this. On my production server after opening the console, spring keeps active, consuming memory, only way to kill it until now:
ps ax | grep spring | cut -f1 -d' ' | xargs kill
only way to kill it until now:
ps ax | grep spring | cut -f1 -d' ' | xargs kill
$ pkill spring
does the job for me ;-)
Guys, why are you using spring on production or CI?
I honestly don't remember which project this was for now, but I most certainly wasn't trying to use spring in production or CI. The reason I opened the bug is that it was trying to run in CI, even though I explicitly disabled it.
@RobinClowers Is it legal to reply messages on github so fast?