How to kill run-z process

[Muromi-Rikka]

Commands started with run-z are not terminated by ctrl+c

[surol]

Operating system?

[Muromi-Rikka]

@surol operating system use windows11 ,windows terminal with powershell

[surol]

@Muromi-Rikka I have tried both PowerShell and cmd. Both terminate the process on Ctrl+C.
May be, this is related to some specific sub-process? Can you provide a small repro?

[Muromi-Rikka]

@surol I use pnpm workspace
root package.json

{
  "scripts": {
    "all":"run-z serve:sunna,serve:lumina,watch:common",
    "serve:sunna": "pnpm --filter sunna start:dev",
    "serve:lumina": "pnpm --filter lumina start",
    "watch:common": "tsc --watch --project ./apps/common"
  },
  "devDependencies": {
    "@angular/cli": "^13.3.0",
    "@nestjs/cli": "^8.2.3",
    "run-z": "^1.10.0"
  }
}

lumina start:

{"start": "ng serve"}

sunna start:

{"start:dev": "nest start --watch"}

[surol]

I don't believe this is related to run-z.

The Ctrl+C (SIGINT) is sent to the whole process group. So, all of lumina, sunna, and tsc receive it. It's up to them to terminate properly. It seems that one of them fail to do so.

You can try npm-run-all and its run-p command instead. It seems you are not using run-z capabilities anyway.

[iki]

@surol I have the same issue, run-p closes the running nodemon correctly, run-z leaves the process running (with server port open and working). On Windows 11 too. Would be great to fix it.

[Muromi-Rikka]

@iki try use google/wireit

[surol]

Version 1.10.1 should fix the issue. At least, it fixes it for run-z/triage-sigint.

If the issue still present for you, please help me find out the reason by providing a repro. E.g. by creating a PR for run-z/triage-sigint.