-
Notifications
You must be signed in to change notification settings - Fork 52
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
use child_process.spawn
instead of child_process.exec
to avoid maxBuffer exceeded
#23
Comments
Could you send a PR? |
Sorry, i'm not good at coffeescript. |
js2coffee is your friend :) |
I've run into this issue as well. A quick solution would be to make the 'maxBuffer' option configurable somehow: http://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback |
+1, also suffering from this error. @Dragony, making it configurable would not be a good solution. |
+1 |
Have you implemented this in your fork @NecoleYu? |
The `exec` call in `git.coffee` will be replaced soon but this fixes the issues for now. Closes #23.
exec's default
maxBuffer
is 200k, if the files in repository are huge, e.g. cdnjs, will cause the errorError: stdout maxBuffer exceeded
.Using spawn can avoid this error.
The text was updated successfully, but these errors were encountered: