pm2@3.3.1 not support "uncaughtException"? Is this an exception or something else?
Open
Nobody has claimed this yet.
T: Bug
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
I used 'pm2@3.2.9' earlier, which supports' uncaughtException '. The node program has no abnormal exit and restart
However, now I use 'pm2@3.3.1', it seems that it does not support 'uncaughtException ', and the node program is restarted after the abnormal exit
My English is not good, with the help of translation software translation, please forgive me
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
The report names no source file, test, or entry point. Start by reproducing the uncaughtException behavior with pm2@3.2.9 and pm2@3.3.1, then identify the relevant process-management path and add a regression test showing whether the process should restart or remain running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100