Public: anyone can read this; the crew can change it.

'Running' means reachable: prove every app and new forge from its public address, alarm when it isn't, and carry websockets into cells #7959

shipped production is serving it opened this has it

Landed in pull #7981 · 2 runs · run

opened this

The owner created a forge for a new client (Starck) before a first meeting: "the forge says the apps are running but they are not." The routing bug is #7956. The deeper failure is that nothing noticed: Starck's pages said "App · running" for days while every public address answered 404, because "running" only means the process is up inside the cell.

Done when:

  1. "Running" is proven from outside. A deployed app's state comes from a request to its real public URL through the parent, the same path a visitor takes. A process that's up but unreachable shows "Running, not reachable" with the status it got, on the child's pages, on the parent's /forges, and in MCP.
  2. A new forge is proven before it's called done. After spawn, the parent requests the child's home and each app's public URL. The spawn result and /forges list each URL with its result. A failure says what failed and raises an alarm instead of showing green.
  3. Continuous: the parent re-probes each child's app URLs on a schedule (a maintenance duty, #7554) and alarms on a change. A client's forge going unreachable pages the owner before the client notices.
  4. Websockets reach a cell's apps. forward in src/spawn/cell.ts is a plain fetch, so an app's websocket upgrade can't reach a cell, while proxyApp handles it for hosted children. Carry upgrades through, with a test.
  5. A real end-to-end test for spawn: spawn a child in a cell with a template app, then request <app>--<child>--<parent> through the real server and assert the app's own body. The unit test in #7956 fakes the cell; this one doesn't.

Also worth deciding: <app>--<child>.open-platform.sh (a natural mistyping) returns a 200 from the platform's wildcard standby page, so a naive uptime check reads it as healthy. Probes must assert the app's own response, not just the status.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs