mysticatea/npm-run-all

Parallel tasks can't be killed in Webstorm Terminal on Windows

Open

#33 geöffnet am 24. März 2016

Auf GitHub ansehen
 (14 Kommentare) (3 Reaktionen) (0 zugewiesene Personen)JavaScript (5.484 Stars) (271 Forks)batch import
bugevaluatinghelp wanted

Beschreibung

This is admittedly Webstorm specific, but as FYI:

This is the same issue that I reported in Issue 32, but it occurs in Webstorm's terminal on Windows. Hitting Ctrl+C produces the prompt for "Terminate batch job (Y/N)?", but answering "Y" doesn't actually get you back a usable command line. It appears to be using the native Window command line behind the scenes since this is shown when I open the Webstorm terminal:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.

The result of hitting Ctrl+C: ^C^C^CTerminate batch job (Y/N)? Terminate batch job (Y/N)? ^CTerminate batch job (Y/N)? ^^CCTerminate batch job (Y/N)? Terminate batch job (Y/N)? Terminate batch job (Y/N)? ^CTerminate batch job (Y/N)? Terminate batch job (Y/N)? Y

It becomes frozen after answering Y.

Contributor Guide

Tech Stack
javascriptnodejs
Domain
clideveloper experience
Issue Type
bug
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-3 hours
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
stale
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
clear
Voraussetzungen
Node.js basicsWindows OSProcess signals familiarity
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
35
Research-Richtung
Start by examining the signal handling in the npm run all source code, likely in the `src/` directory, focusing on how child processes are spawned and terminated. Review the comments in the issue for any suggested workarounds or fixes. Test the behavior in Webstorm on Windows and compare with other terminals. Consider using Node.js `process.on('SIGINT')` and child process spawn options for Windows compatibility.