did not encounter expected EOF at [onread]
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 922
- Forks
- 281
- PR merge metrics
- No merged PRs in 30d
Description
did not encounter expected EOF at [onread] (D:\ideaworkspace3\btshell2\out\main\index.js:41790:32) at D:\ideaworkspace3\btshell2\out\main\index.js:41771:19 at FSReqCallback.wrapper [as oncomplete] (node:fs:683:5) at FSReqCallback.callbackTrampoline (node:internal/async_hooks:130:17) {path: "E:/download/tabby-1.0.212-portable-x64/resources/app.asar/node_modules/glasstron/native/dwm_exec.exe", syscall: "read", code: "EOF", stack: "Error: did not encounter expected EOF\n at [onre…backTrampoline (node:internal/async_hooks:130:17)", message: "did not encounter expected EOF"}
await tar.c({ file: localTgzPath, gzip: true, cwd: dir }, localPaths.map(p => relative(dir, p)));
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 with the reported tar.c invocation and the node:fs stack trace, noting that the paths shown are generated out/main/index.js and a packaged glasstron executable rather than named repository files. Reproduce the EOF error with the same archive operation and determine the conditions that trigger it. Done means the failure is explained and the relevant behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100