docs/CONSOLE.md shows output `simlock status` never prints
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown, typescript
- Domain
- cli, documentation
Research direction
The mismatch is between the sample output at docs/CONSOLE.md lines 57-62 and what simlock status prints. Compare that block with the status assertion in src/cli/index.test.ts near line 3219 and the status section of docs/CLI.md, and check the daemon start output at src/cli/index.ts around line 1646. Done means the docs example matches the real status output (or the wording is split so each command's output is shown accurately), with the test and CLI.md left consistent.
Written by the indexing model from the issue text.
Description
docs/CONSOLE.md:57-62:
`simlock daemon start` and `simlock status` print the address:
Daemon running
Console: http://127.0.0.1:4700/
Only daemon start prints that first line (src/cli/index.ts:1646). simlock status opens with the health-and-mode line instead — Daemon: running (worker) then Console: … then Host: … — as src/cli/index.test.ts:3219 pins and docs/CLI.md documents. A reader who runs the second command the sentence names does not see the block they were promised; the Console: line they are after is right, the line above it is not.
Found while triaging #422, reading the docs the report cites.
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 1
- Avg merge
- 6h 14m
- Merged PRs (30d)
- 141
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:new
Difficulty 1/5 Under an hour Newbie friendliness 84/100
callstackincubator/simlock#451 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
callstackincubator/simlock#450 ·
Maintainers usually reply within 1 day
-
Lint does not enforce index.ts boundaries for cleanup/, routing/, warm-pool/ and contract/ helpersOpenbug:new
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#445 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/simlock#424 ·
Maintainers usually reply within 1 day
-
daemon-lifecycle e2e: the it.fails status test passes for the wrong reasonPossibly taken @V3RON claimed this 3 days ago. Openbug:triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
callstackincubator/simlock#422 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
area:deploy task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wilanis/wilanis-js#1017 ·
Maintainers usually reply within 1 day
-
documentation v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/servers#5133 ·
Maintainers usually reply within 1 day
-
budget bug feature frontend good-issue medium needs-review OSCI'26 payments
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
SatyamPandey-07/WorkSphere#5990 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lugassawan/swe-workbench#799 ·
Maintainers usually reply within 1 day
-
bug good first issue javascript
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yukikotani231/sqlsift#326 ·
Maintainers usually reply within 1 day