-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Buffer the files in preprocessor to prevent EACCESS errors. #566
Comments
@iammerrick thanks a bunch for looking into this! I know about this issue and yep, it has to be fixed asap. I need to look into it more, there are multiple things how to improve it. Using graceful-fs is probably the first thing we should do... |
iammerrick
added a commit
to iammerrick/karma
that referenced
this issue
Jun 15, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the preprocessor functionality is not resilient to a large number of files... At the small number of 256 you will reach the Mountain Lion limit... The solution to this is to implement a buffer that queues requests beyond a particular limit and flushes them accordingly. @isaacs has an implementation of this as a drop in replacement for
fs
called node-graceful-fs. The tests do not pass when we drop this in however, I think because karma is mockingfs
.From my perspective we have two options...
fs
mocking to not collide with node-graceful-fs, not really sure how to do this currently, the problem is still unclear to me.Please let me know which approach you want to take and I will look into implementing it. Currently our project can't use preprocessing because of this limitation.
(I don't consider calling ulimit as a viable solution.)
The text was updated successfully, but these errors were encountered: