mysticatea/npm-run-all

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

Open

#33 aberto em 24 de mar. de 2016

Ver no GitHub
 (14 comments) (3 reactions) (0 assignees)JavaScript (5.484 stars) (271 forks)batch import
bugevaluatinghelp wanted

Description

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.

Guia do colaborador

Pilha de tecnologia
javascriptnodejs
Domain
clideveloper experience
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
clear
Prerequisites
Node.js basicsWindows OSProcess signals familiarity
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
35
Direção de pesquisa
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.