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

CLI reports its auto-launch timeout as INTERNAL while MCP reports the same failure as DAEMON_STARTUP_FAILED

Closed
  • Is something wrong?
#672 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start by reading src/cli/index.ts around line 246, then compare its launch timeout handling with src/mcp/connect.ts and the error contract in src/contract/errors.ts. Check the CLI tests for auto-launch timeout behavior and the expected error code; done when the CLI reports the same DAEMON_STARTUP_FAILED code as MCP for that timeout while keeping the documented exit code.

Written by the indexing model from the issue text.

Description

bug:new

Two frontends run the same launch-then-retry policy with the same 5 s deadline hard-coded in each, and disagree on what the failure is called.

  • src/cli/index.ts:246 throws a plain Error, so runCli maps it to INTERNAL (exit 1).
  • src/mcp/connect.ts:51,62 throws SimlockError("DAEMON_STARTUP_FAILED") for the same event; that code exists in the contract's table with cliExitCode: 1 (src/contract/errors.ts:214).

docs/CLI.md:22 says INTERNAL is for "anything unexpected", so the CLI labels an anticipated timeout — the one failure mode its own auto-launch exists to wait through — as an unexpected internal error. An agent scripting the CLI cannot tell "the daemon is slow, retry later" from a crash.

The deadline being written twice is architecture rule 10 (a constant known to one module, asked of it through its surface); the divergent code is what that duplication already produced.

Found while triaging #663.

Written by an agent.

Dominant language
TypeScript
Stars
20
Forks
2
Avg merge
8h
Merged PRs (30d)
316

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.