Ensure force kill timeout isn't keeping process alive #7
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.
π I don't know if you still use this module? I was checking it out in relation to something similar I'm working on and noticed what I think is a bug.
I thought I'd throw this PR up quickly β I didn't add any tests but I did run the existing ones and they apssed. I'm pretty sure the behaviour of this module would be to wait up to
forceTimeout
ms every time the process is killed in non-dev envs because the timeout would keep the event loop non-empty.See
unref()
for more info.