-
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
pipe(): Too many open files #1537
Comments
After several runs, the issue manifests as
Also, this was observed on OSX. |
I'm getting a similar error because of too many files open:
This should just be written with something like the async.js library: https://github.com/jashkenas/coffee-script/blob/master/src/command.coffee#L106 |
I'm getting the same error that @viatropos on OSX : coffee -b -c -w -l ../
/Users/***/Sites/***/tmp/bin/nodejs/node_modules/coffee-script/lib/coffee-script/command.js:287
if (e.code !== 'ENOENT') throw e;
^
Error: watch EMFILE
at errnoException (fs.js:636:11)
at FSWatcher.start (fs.js:663:11)
at Object.watch (fs.js:691:11) If I run this command on a smallest folder, it's work. |
@craSH, @viatropos -- I have been using It seems odd that system settings, i.e. file descriptor limit, should cause a scaling issue. I feel as though the program should wait until a file descriptor becomes available rather than throw. However, I'm still unsure about what level this type of error should be handled at. |
@braddunbar different craSH - you meant @Crash-- ;) cheers! |
I just encountered the
and so on. I've reported this as Node issue #2479. For now, you should work around it by only using |
Ben Noordhuis has stated that there's nothing Node (or CoffeeScript) can do to work around this limit; you can modify it at the OS level using So, closing this issue. We should probably ignore hidden subdirectories to get around the git repo case. |
Reopening to ignore hidden subdirectories ;) |
Closed by 127653b. |
I'm experiencing this with version 1.4.0. In the directory I'm trying to watch, there is a symlink to another directory. Total number of files is less than 300. If I remove the symlink, the problem goes away. Using OSX Mountain Lion. |
When running
coffee
on a directory with a large number of files (329 to be exact), I receive the following error:The failure seems to center on the call to
mkdir -p
. I've yet to find a way to fix this cleanly.The text was updated successfully, but these errors were encountered: