-
Notifications
You must be signed in to change notification settings - Fork 2k
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
EMFILE + ENOSPC errors swallowed by Grunt hook instead of being logged as errors #3523
Comments
As a side note, it seems that there are other issues with [email protected]. Changes to deeply nested files are not noticed-- switching to |
Created separate issue for the issue with |
Just verified that this actually happening on Full details: ∑ npm -v
2.8.4
∑ node -v
v0.10.26 "grunt": "0.4.5",
"grunt-contrib-clean": "0.6.0",
"grunt-contrib-coffee": "0.13.0",
"grunt-contrib-concat": "0.5.1",
"grunt-contrib-copy": "0.5.0",
"grunt-contrib-cssmin": "0.9.0",
"grunt-contrib-jst": "0.6.0",
"grunt-contrib-less": "1.1.0",
"grunt-contrib-uglify": "0.7.0",
"grunt-contrib-watch": "0.5.3",
"grunt-sails-linker": "0.10.1",
"grunt-sync": "0.2.4",
|
Argh- meant to say If you're reading this and haven't had to deal w/ EMFILE errors before, here's how you solve it on OS X for reference: ulimit -n 1024 ^^ that'll last as long as a terminal window is open. Also note that more recent versions of OS X don't allow you to specify a ulimit much higher than
|
For reference:
In Sails v0.11.3, with:
EMFILE errors from Grunt are being swallowed (logged as verbose), e.g.:
Haven't had a chance to test yet to see if this is occurring in 0.11.4 or the 0.12.0 prerelease, but leaving this as a note in the mean time.
The text was updated successfully, but these errors were encountered: