mafintosh / mafintosh/why-is-node-running
isn't SIGUSR1 reserved for the debugger?
Open
breaking change
bug
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
In the [docs](https://nodejs.org/api/process.html):
> 'SIGUSR1' is reserved by Node.js to start the debugger. It's possible to install a listener but doing so might interfere with the debugger.
SIGUSR2 should be ok
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the signal-handling entry point and the linked Node.js process documentation. Confirm how SIGUSR1 is currently used, then change or document the behavior so it does not interfere with the debugger; done means the selected signal is safe and the project still reports why Node is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100