WriteStream
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?
How could we reproduce this issue?
Supporting information
$ pm2 report
C:\Users\IPE-1352.pm2\pm2.log last 20 lines:
PM2 | at next (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\node_modules\async\waterfall.js:96:20)
PM2 | at C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\node_modules\async\internal\onlyOnce.js:12:16
PM2 | at WriteStream. (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\lib\Utility.js:186:13)
PM2 | at WriteStream.emit (node:events:527:28)
PM2 | at WriteStream.emit (node:domain:537:15)
PM2 | at node:internal/fs/streams:72:16 {
PM2 | errno: -4094,
PM2 | code: 'UNKNOWN',
PM2 | syscall: 'spawn'
PM2 | }
PM2 | at Object.God.logAndGenerateError (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\lib\God\Methods.js:34:15)
PM2 | at C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\lib\God\ForkMode.js:115:13
PM2 | at wrapper (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\node_modules\async\internal\once.js:12:16)
PM2 | at next (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\node_modules\async\waterfall.js:96:20)
PM2 | at C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\node_modules\async\internal\onlyOnce.js:12:16
PM2 | at WriteStream. (C:\Users\IPE-1352\AppData\Roaming\npm\node_modules\pm2\lib\Utility.js:186:13)
PM2 | at WriteStream.emit (node:events:527:28)
PM2 | at WriteStream.emit (node:domain:537:15)
PM2 | at node:internal/fs/streams:72:16
PM2 | at FSReqCallback.oncomplete (node:fs:188:23)
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
Start by reproducing the Windows error with the provided PM2 log and running pm2 report. Trace the failure through lib/Utility.js, lib/God/Methods.js, and lib/God/ForkMode.js; the issue is complete when the WriteStream/spawn failure is understood and a verified fix or clear diagnosis is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100