child_process: cleanup AbortSignal code duplication#37823
Closed
Uh oh!
There was an error while loading. Please reload this page.
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.
This PR cleans-up AbortSignal code duplication between fork/exec and spawn (which seem to share the same essential implementation). Removed
spawnWithSignal, and all logic is now inspawn.This PR does have two behaviour changes:
fork/execFile, where before forfork/execFilean abort caused an abort in next-tick, while now it'll callabortin the same tick (a pre-aborted signal still aborts in next-tick as before). The behaviour forspawnis unchanged.child.spawn()is called, so that ifchild.spawn()throws, the signal won't keep a reference to the "bad" child-process.