-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: add Windows-specific info to subprocess.kill
#34867
doc: add Windows-specific info to subprocess.kill
#34867
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
Not a blocker: I'd put this just after the Linux specification and before code example.
Looks good to me, thanks! |
@nodejs/child_process |
8d40f81
to
28587cd
Compare
Who do we need to give the OK and merge this in? I see @jasnell approved it, not sure if he can merge it. |
doc/api/child_process.md
Outdated
@@ -1133,6 +1133,10 @@ may not actually terminate the process. | |||
|
|||
See kill(2) for reference. | |||
|
|||
On Windows the child process will be forcefully terminated since | |||
`SIGKILL` and `SIGTERM` signals are not available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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).
@joaolucasl This needs a rebase, and there is one comment left that needs to be addressed before landing. |
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. |
Will update it this week. |
@joaolucasl - looks like this PR have gotten a little stuck. need a rebase to resolve git conflicts |
7160bc5
to
c0ba12a
Compare
I rebased, fixed the merge conflict, fixed the lint error, squashed, and force pushed. |
c0ba12a
to
57f3583
Compare
Sorry for the huge delay in updating this. Thanks @zenflow for the suggestion. Ready for review! |
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 <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
57f3583
to
504ed7c
Compare
Landed in 504ed7c |
Clarify the inner workings of .kill on Windows, since termination signals are not available there. Fixes: #34858 PR-URL: #34867 Reviewed-By: Juan José Arboleda <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Clarify the inner workings of .kill on Windows, since termination signals are not available there. Fixes: #34858 PR-URL: #34867 Reviewed-By: Juan José Arboleda <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
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 viaprocess_wrap
.Fixes: #34858
Checklist