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

doc: add Windows-specific info to subprocess.kill #34867

Merged
merged 1 commit into from Mar 30, 2021

Conversation

Copy link
Contributor

@joaolucasl joaolucasl commented Aug 21, 2020

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

@nodejs-github-bot nodejs-github-bot added child_process doc labels Aug 21, 2020
Copy link
Member

@juanarbol juanarbol left a comment

Nice.

Not a blocker: I'd put this just after the Linux specification and before code example.

@s4m0r4m4
Copy link

@s4m0r4m4 s4m0r4m4 commented Aug 22, 2020

Looks good to me, thanks!

@targos
Copy link
Member

@targos targos commented Aug 22, 2020

@joaolucasl joaolucasl force-pushed the docs/windows-child-process-kill branch from 8d40f81 to 28587cd Compare Aug 22, 2020
@s4m0r4m4
Copy link

@s4m0r4m4 s4m0r4m4 commented Sep 9, 2020

Who do we need to give the OK and merge this in? I see @jasnell approved it, not sure if he can merge it.

@@ -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.
Copy link
Contributor

@zenflow zenflow Sep 12, 2020

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).

@DerekNonGeneric DerekNonGeneric added the windows label Sep 13, 2020
@aduh95
Copy link
Contributor

@aduh95 aduh95 commented Nov 8, 2020

@joaolucasl This needs a rebase, and there is one comment left that needs to be addressed before landing.

@aduh95 aduh95 added the stalled label Nov 8, 2020
@github-actions
Copy link

@github-actions github-actions bot commented Nov 8, 2020

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.

@joaolucasl
Copy link
Contributor Author

@joaolucasl joaolucasl commented Nov 9, 2020

Will update it this week.

doc/api/child_process.md Outdated Show resolved Hide resolved
doc/api/child_process.md Outdated Show resolved Hide resolved
@PoojaDurgad
Copy link
Contributor

@PoojaDurgad PoojaDurgad commented Dec 28, 2020

@joaolucasl - looks like this PR have gotten a little stuck. need a rebase to resolve git conflicts

@Trott Trott force-pushed the docs/windows-child-process-kill branch from 7160bc5 to c0ba12a Compare Jan 8, 2021
@Trott
Copy link
Member

@Trott Trott commented Jan 8, 2021

I rebased, fixed the merge conflict, fixed the lint error, squashed, and force pushed.

doc/api/child_process.md Outdated Show resolved Hide resolved
@joaolucasl joaolucasl force-pushed the docs/windows-child-process-kill branch from c0ba12a to 57f3583 Compare Mar 26, 2021
@joaolucasl
Copy link
Contributor Author

@joaolucasl joaolucasl commented Mar 26, 2021

Sorry for the huge delay in updating this. Thanks @zenflow for the suggestion.

Ready for review!

@aduh95 aduh95 added author ready review wanted labels Mar 26, 2021
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>
@Trott Trott force-pushed the docs/windows-child-process-kill branch from 57f3583 to 504ed7c Compare Mar 30, 2021
@Trott
Copy link
Member

@Trott Trott commented Mar 30, 2021

Landed in 504ed7c

@Trott Trott merged commit 504ed7c into nodejs:master Mar 30, 2021
13 checks passed
MylesBorins pushed a commit that referenced this issue Apr 4, 2021
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 <soyjuanarbol@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Apr 4, 2021
targos pushed a commit that referenced this issue May 1, 2021
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 <soyjuanarbol@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@danielleadams danielleadams mentioned this pull request May 3, 2021
@joaolucasl joaolucasl deleted the docs/windows-child-process-kill branch Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready child_process doc review wanted stalled windows
Projects
None yet
Development

Successfully merging this pull request may close these issues.