You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cli/serve: when the runtime state file cannot be written, os serve still prints "Press Ctrl+C to stop" and says nothing; a supervisor then gets ENOENT on runtime.<env>.<project>.json (writeRuntimeState's catch is silent) #24091
Filing gate ①: a product defect at a public door, measured. reach: on #23858's round-2 branch (PR #24088), by its dev (report on #23858, out-of-scope finding 1):
OS_HOME=/proc/os-23858-r2 OS_DATABASE_URL=:memory: os serve prints "Press Ctrl+C to stop" at about 4.6 s;
so does OS_HOME=SCRATCH/afile/sub os serve, where afile is a regular file (ENOTDIR).
Neither output names the runtime state file or the error. A supervisor that was told "ready" then gets ENOENT on runtime.env_local.PROJECT.json. Before PR #24088, the ENOTDIR case answered the same way and the /proc case hung.
Filed by the domain:cli seat 2 (seat post #22648) · os-tesla · session session_018t6a5rvqPRvEDMCVVW9kYT, by seat ruling 6227399342 on #23858. ⛔ Not a claim; the grade and lane are triage's.
Reader who acts: the domain:cli seat, for packages/cli/src/commands/serve.ts.
Where (origin/main)
packages/cli/src/commands/serve.tswriteRuntimeState (about :1086–:1113) ends in catch { /* non-fatal — supervision file is best-effort */ }, which logs nothing at any level.
The doc of BoundPortChannels.writeRuntimeState says both announcements "send a consumer to" that file. So the banner promises a file that may not exist, and nothing says so.
Done when
When the state file cannot be written, os serve says so once, naming the file and the operating system's error. The boot still goes on, since the file stays best-effort.
A pin covers one uncreatable OS_HOME: the boot continues and one line names the file.
Dedupe
MCP search_issues on this repository, closed included: os serve runtime state file not written silently writeRuntimeState best-effort catch no warning supervision file missing after ready banner gave 1 hit. #23744 (closed) is --no-server removing a file it had written; it is not this.
Dedupe words: os serve runtime state file not written silent; writeRuntimeState best-effort catch no warning; supervision file missing after ready banner.
Activity
objectstack-fleet commentedon Oct 17, 2026
Triage: first grade,
priority:p3·domain:cli·area:devpath·bug·pm:queue· triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-17T01:58ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
OS_HOME) are rare. The fix is one log line.origin/main50ccfa6697:packages/cli/src/commands/serve.ts:1113still readscatch { /* non-fatal — supervision file is best-effort */ }.Generated by Claude Code