Console lane deletes a failed daemon's home, so a start failure names no cause
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- developer-experience, testing
Research direction
Start in e2e/console/fixtures.ts at startDaemon and dispose (lines 112-116 and 167-171), then inspect how the console lane reports a failed start. Reproduce the failed-start case described in the issue and check whether daemon.log remains available or its tail appears in the failure output. Done when the failure preserves enough log information to distinguish startup causes.
Written by the indexing model from the issue text.
Description
When startDaemon's simlock daemon start fails, its catch calls dispose, which runs rm(home, { force: true, recursive: true }) (e2e/console/fixtures.ts:112-116, 167-171). That deletes daemon.log — the only record of why the daemon did not come up.
The lane's failure line is then the CLI's own give-up message, which is the same for every cause: a daemon still booting, a daemon that died binding its HTTP port (the EADDRINUSE family, #553), or a daemon that failed driver discovery. Verified: a driver module that fails to import produces Timed out starting simlock daemon: connect ENOENT <home>/daemon.sock, exit 1, byte-identical to a slow boot.
A failed start should keep the log (or print its tail into the failure) so the next occurrence names its cause instead of being guessed at.
Found while triaging #663.
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 1
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 247
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from callstackincubator/simlock
-
bug:needs-info
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#657 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 3/5 1-2 days Newbie friendliness 70/100
callstackincubator/simlock#672 ·
Maintainers usually reply within 1 day
-
Flaky console lane: CLI auto-launch's fixed 5 s deadline expires while a daemon starts on a loaded runner (ENOENT daemon.sock)Possibly taken @V3RON claimed this today. Openbug:ready flaky-test
callstackincubator/simlock#663 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Make code review incremental, risk-routed and measurablePossibly taken @V3RON claimed this today. Opentask:ready
callstackincubator/simlock#654 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ranxianglei/billion-context#3583 ·
Maintainers usually reply within 1 day
-
documentation v3
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anomalyco/opencode#56380 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NIAEFEUP/website-niaefeup-frontend#489 ·
Maintainers usually reply within 2 days