Figure out why it takes two SIGINTs to fully exit a process
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
go run cmd/react/main.go
| Listening on http://0.0.0.0:3000
^C^Csignal: interrupt
vs. removing signals
cli := cli.New("react", "react development server").Signals(nil)
go run cmd/react/main.go
| Listening on http://0.0.0.0:3000
^Csignal: interrupt
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the behavior with go run cmd/react/main.go, then compare it with cli.New("react", "react development server").Signals(nil). Inspect the signal handling around the CLI setup in cmd/react/main.go; done means the development server exits after one SIGINT while retaining normal signal handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100