fix: not sending SIGINT to npm install subprocess#56
Merged
Matthew-Mallimo merged 1 commit intomainfrom Apr 24, 2026
Merged
Conversation
dominic-farquharson
approved these changes
Apr 17, 2026
guym4c
approved these changes
Apr 17, 2026
ddwivedi551
approved these changes
Apr 20, 2026
code-forger
approved these changes
Apr 24, 2026
Matthew-Mallimo
force-pushed
the
fix/sigintPropagation
branch
from
5e60d06 to
0ea0b77
Compare
Matthew-Mallimo
force-pushed
the
fix/sigintPropagation
branch
from
0ea0b77 to
d0278e7
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
When running a CUT template, if you sent a SIGINT signal (CTRL + C) during the npm install phase, the CUT process would exit, but not the npm install process.
This change now properly relays the SIGINT signal to the npm install subprocess.