Check for SIGTERM exit code #155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
floatdrop
force-pushed
the
set-kill-code-to-zero
branch
from
e0e43b8 to
04c687b
Compare
floatdrop
changed the title
sindresorhus
added a commit
that referenced
this pull request
Nov 8, 2015
Check for SIGTERM exit code
|
Oh wow. I would honestly never have thought of this. Thanks again @floatdrop :) |
novemberborn
added a commit
that referenced
this pull request
Mar 23, 2016
The child process is no longer killed from the main process, instead it exits upon receiving an 'exit' message. This makes the changes from <#155> redundant.
This was referenced Sep 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related - nodejs/node-v0.x-archive#8667
Closes #154.