Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Flaky console lane: CLI auto-launch's fixed 5 s deadline expires while a daemon starts on a loaded runner (ENOENT daemon.sock)

Open
  • Is something wrong?
#663 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@V3RON is already working on this.

Since Oct 17, 2026.

  • #674 by @V3RON — open

Assessment

This issue has not been assessed yet.

Description

bug:ready flaky-test

What happens

Console lane, once in 198 recent Console job runs (run 38955614485, main at 93ffed8f, webkit):

Error: {"error":{"code":"INTERNAL","message":"Timed out starting simlock daemon: connect ENOENT /tmp/simlock-console-GGA6zr/daemon.sock"}}
    expect(received).toBe(expected)
    Expected: 0
    Received: 1
    > 110 |     expect(started.code, started.stderr).toBe(0);
        at start (e2e/console/fixtures.ts:110:42)

A rerun of the same job passed.

What is known

  • The message is thrown by the CLI's auto-launch, not the fixture: src/cli/index.ts:234-246
    launches the daemon and polls the unix socket for a fixed 5 s. A daemon that needs longer to
    create its socket on a loaded runner makes daemon start exit 1 while the daemon keeps booting.
  • The console lane's startDaemon (e2e/console/fixtures.ts:108-111) has no retry; the vitest
    lane's withHttpDaemon (e2e/helpers/http-daemon.ts) retries exactly this error family (#553),
    so the same class is already known in the other lane.
  • Distinct from #642: that one is a route.fetch refused after teardown disposes a live gateway;
    this one is startup slowness before any test code runs.

Found while triaging #642.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstackincubator/simlock

All issues in callstackincubator/simlock

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.