pm2 does not let yarn exit when its child process is killed
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Please check this issue:
https://github.com/yarnpkg/berry/issues/5786
yarn behaves as spected when run on its own.
But when it is pm2 that runs it, yarn would not terminate when its child gets killed.
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 issue names no PM2 files, tests, or entry points; start by reading the linked Yarn issue and reproducing the behavior with Yarn running under PM2 while its child process is killed. Trace the process-exit handling and consider the work complete when Yarn terminates as it does when run directly, with coverage for this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100