-
Notifications
You must be signed in to change notification settings - Fork 404
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
[BUGFIX] Prevent leaked runners/sub processes. #1205
Conversation
@johanneswuerbach / @rwjblue / @krisselden r? |
Looks good to me, could you remove the |
977112b
to
79ea457
Compare
It is not uncommon during developer to end the process unexpectedly. Examples are <ctr-c>, crash, etc. Switching to `execa` gives us * automatic cleanup of child_processes in the above scenarios * Promise API * other nice things: https://github.com/sindresorhus/execa#why
79ea457
to
184de4e
Compare
The remaining Travis Task was OSX, which is having some trouble. Prior to dropping the lock file it was green, and I have now been waiting 1+ day for the job to be executed. Local test suggest all is well, as was the last CI run... So I am making the judgement call to skip it. |
@johanneswuerbach I believe we must release 2.x correct (as i see a previous commit changed the support matrix) ? Should I just do that now? |
@stefanpenner done, support about the delay. |
@johanneswuerbach nice thanks! |
@johanneswuerbach now that we support only newer node, any opposition to me modernizing the codebase? |
Definitely not! Happy to review any upcoming PRs. |
It is not uncommon during developer to end the process unexpectedly. Examples are , crash, etc.
Switching to
execa
gives us