Skip to content

Conversation

bjornstar
Copy link

And bump batch version to v0.5
And cache configs on the root builder.

Bjorn Stromberg added 2 commits December 12, 2013 21:24
@bjornstar
Copy link
Author

A little background on this issue. I was having problems with "too many files open" on one of my projects - #66 😢

Since this project uses batch I thought I'd just bump the batch version number and see if that solved my problem.

It got rid of the "too many open files" problem and replaced it with callbacks never getting called 🌵

It turns out that batch silently fails when the maximum call stack size is exceeded. 😠

So, I wrapped the recursive calls in buildAliases in a process.nextTick to avoid the issue. You should really fix this in batch, though.

@jonathanong
Copy link
Contributor

why not just open a PR or issue in batch?

@bjornstar
Copy link
Author

Because it still needs to be fixed here and I have no idea what requirements batch has. At least this is node only and I don't have to worry about process.nextTick not existing.

@jonathanong
Copy link
Contributor

@visionmedia plz fix batch :D

@tj
Copy link
Contributor

tj commented Dec 29, 2013

dont need aliases anymore

@tj tj closed this Dec 29, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants