fix: Treats natural node.js process termination as exit code 0 #24
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.
Issue
node.js natural process termination triggered an exit code of
128
, caused by the asynchronousbeforeExit
event.Fix
Changes the asynchronous
beforeExit
to trigger with an exit code 0, mirroring the behavior used the PM2 eventSummary of Changes - patch level change
/fixtures
directory (when you create the third fixture, you'll probably need the 4th down the line and this makes it clear where they go)empty
fixture that replicates the bug reported in 23index.js
Fixes #23