PM2 Keyboardinterrupt Error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
When I do pm2 logs followed by the process name, such as pm2 logs testing, the logs display as expected. However, the only way I can exit the logs is by using ctrl + c. This action triggers a keyboardinterrupt error, disrupting the process completely. Despite attempting various solutions, such as code modifications and restarting or reloading the process (pm2 restart testing for example), the error persists and remains unresolved. I can't find any guides on this issue either.
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
Reproduce the issue with pm2 logs testing, then stop the log stream with Ctrl+C and observe the reported KeyboardInterrupt error. Trace the CLI log-streaming and interruption handling from this command; done means Ctrl+C exits cleanly without disrupting the managed process, and subsequent commands such as pm2 restart testing still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100