Discord Username / User ID
interferon0
What does this improvement do?
Without a handler, Node kills the process abruptly on Ctrl+C during a long test run --wait, leaving the user unsure whether the run was cancelled or still executing server-side (it is: the CLI only polls; the run lives on the backend). This installs a SIGINT handler that prints a one-line explanation plus how to resume (testsprite test list / testsprite test wait ) and exits with the conventional signal code 130.
Details / implementation notes
New src/lib/interrupt.ts (message + exit 130), wired once in src/index.ts. process is injectable so it is unit-tested without spawning a subprocess (2 tests). Full gate green. PR to follow once assigned.
Confirmations
Discord Username / User ID
interferon0
What does this improvement do?
Without a handler, Node kills the process abruptly on Ctrl+C during a long test run --wait, leaving the user unsure whether the run was cancelled or still executing server-side (it is: the CLI only polls; the run lives on the backend). This installs a SIGINT handler that prints a one-line explanation plus how to resume (testsprite test list / testsprite test wait ) and exits with the conventional signal code 130.
Details / implementation notes
New src/lib/interrupt.ts (message + exit 130), wired once in src/index.ts. process is injectable so it is unit-tested without spawning a subprocess (2 tests). Full gate green. PR to follow once assigned.
Confirmations