Skip to content
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 exec #38

Closed
wants to merge 6 commits into from

Conversation

gustavohenke
Copy link

Hey @notatestuser,
I tried to implement the usage of child_process.spawn method instead of child_process.exec to avoid errors as reported in #23.

I'm opening this PR so we can discuss the changes and fix possible errors - unfortunately I'm a Windows developer, so I couldn't run successfully all tests (I'm hoping Travis will tell me what's wrong).

Thanks in advance!

Fixes #23

@notatestuser
Copy link
Owner

Sounds good to me. Is there a chance you could fix up that test case?

@gustavohenke
Copy link
Author

Of course!

Gustavo Henke added 4 commits September 26, 2014 12:41
To keep compatibility with child_process.exec(), which did create an
exception when the process exited with error code, we'll do this as well.
 child_process.spawn() already places quotes around arguments that
 have spaces, so we don't need to do this by ourselves.
@gustavohenke
Copy link
Author

@notatestuser I have the tests passing locally, but in Travis stuff is not going well.
Any opinion?

@gustavohenke
Copy link
Author

btw: I have created a Ubuntu VM and all tests were passing.
So, it seems to not be a problem related to my Windows machine.

@notatestuser
Copy link
Owner

Hmm okay, I'll give it a check.

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.

use child_process.spawn instead of child_process.exec to avoid maxBuffer exceeded
2 participants