Watch mode 'stuck' after Ctrl+C
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 44
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 22
Description
After running the network in watch mode using `npm run network:start` and interrupting the network using Ctrl+C the network is pruned but it doesn't get back to the terminal and it needs an extra Ctrl+C.
See the image below:

The file where this script is executed is [chaincode-dev-start.sh](https://github.com/GalaChain/sdk/blob/main/chain-cli/network/chaincode-dev-start.sh)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with chain-cli/network/chaincode-dev-start.sh and reproduce the issue using npm run network:start, then interrupt it with Ctrl+C. Check why the network is pruned but the terminal remains occupied; done means one Ctrl+C both prunes the network and returns control to the terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100