hexo-admin deploy 出现Error: spawn UNKNOWN 的错误
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 299
- PR merge metrics
- No merged PRs in 30d
Description
EEE { Error: spawn UNKNOWN
at ChildProcess.spawn (internal/child_process.js:366:11)
at spawn (child_process.js:538:9)
at module.exports (C:\Users\彬彬\Desktop\blog\node_modules\hexo-admin\deploy.js:14:14)
at C:\Users\彬彬\Desktop\blog\node_modules\hexo-admin\api.js:413:7
at C:\Users\彬彬\Desktop\blog\node_modules\hexo-admin\api.js:141:7
at call (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:239:7)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:183:5)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at next (C:\Users\彬彬\Desktop\blog\node_modules\connect\index.js:161:14)
at C:\Users\彬彬\Desktop\blog\node_modules\body-parser\lib\read.js:130:5
at invokeCallback (C:\Users\彬彬\Desktop\blog\node_modules\raw-body\index.js:224:16)
at done (C:\Users\彬彬\Desktop\blog\node_modules\raw-body\index.js:213:7)
at IncomingMessage.onEnd (C:\Users\彬彬\Desktop\blog\node_modules\raw-body\index.js:273:7)
at IncomingMessage.emit (events.js:194:15) errno: 'UNKNOWN', code: 'UNKNOWN', syscall: 'spawn' }
Contributor guide
No contributing guide indexed for this repository
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 deploy failure and read deploy.js at line 14, then trace how api.js invokes it at line 413. Identify why the child-process spawn returns UNKNOWN and verify that the deploy action completes without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100