open-cli-tools / open-cli-tools/concurrently
Ctrl+C does not terminate dotnet watch under concurrently, but works with --raw
Open
Nobody has claimed this yet.
pending for input
- Dominant language
- TypeScript
- Stars
- 7.9k
- Forks
- 281
- Avg merge
- 17h 12m
- Merged PRs (30d)
- 1
Description
Describe the bug
Description
When running dotnet watch run through concurrently, pressing Ctrl+C
does not return control to the shell.
The same command exits correctly when run directly, and it also exits
correctly when concurrently is run with --raw.
Reproduction
Environment:
- OS: Debian 13
- concurrently: 10.0.5
- .NET SDK: 10.0.400
- .NET runtime: 10.0.11
- Architecture: x64
Run:
npx concurrently "dotnet watch run"Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing npx concurrently "dotnet watch run" on Debian and compare Ctrl+C behavior with running the command directly and with concurrently --raw. Trace how concurrently handles termination signals for the child process; done means Ctrl+C returns control to the shell without requiring --raw.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100