| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Nice.
Not a blocker: I'd put this just after the Linux specification and before code example.
Sorry, something went wrong.
|
Looks good to me, thanks! |
Sorry, something went wrong.
|
@nodejs/child_process |
Sorry, something went wrong.
|
Who do we need to give the OK and merge this in? I see @jasnell approved it, not sure if he can merge it. |
Sorry, something went wrong.
There was a problem hiding this comment.
Should this say SIGINT and SIGTERM instead?
If I'm not mistaken, SIGINT isn't available here either.
And SIGKILL, if available, forcibly terminates (so it's unavailability doesn't help explain why child process must be forcefully terminated.. SIGKILL wouldn't be useful for avoiding forceful termination anyways).
Sorry, something went wrong.
|
@joaolucasl This needs a rebase, and there is one comment left that needs to be addressed before landing. |
Sorry, something went wrong.
|
This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open. |
Sorry, something went wrong.
|
Will update it this week. |
Sorry, something went wrong.
|
@joaolucasl - looks like this PR have gotten a little stuck. need a rebase to resolve git conflicts |
Sorry, something went wrong.
|
I rebased, fixed the merge conflict, fixed the lint error, squashed, and force pushed. |
Sorry, something went wrong.
|
Sorry for the huge delay in updating this. Thanks @zenflow for the suggestion. Ready for review! |
Sorry, something went wrong.
Clarify the inner workings of .kill on Windows, since termination signals are not available there. Fixes: nodejs#34858 PR-URL: nodejs#34867 Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
| Back | FazBrowse Home | New Git URL |
Clarify the inner workings of subprocess.kill() on Windows,since termination signals are not available there.
I used the the LibUV docs to make sure that this was the actual behaviour, after noticing the code on internal/child_process would ultimately call it via process_wrap.
Fixes: #34858
Checklist