Skip to content

Round 12: infra start timer from the request, booting containers read as starting, start-then-reply, export names its secrets - #56

Merged
qfeuilla merged 1 commit into
mainfrom
deploy
Oct 8, 2026
Merged

qfeuilla merged 1 commit into
mainfrom
deploy

Conversation

@qfeuilla

@qfeuilla qfeuilla commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Fixes from Tangle's round 12.

  • R12-1: the next-step export hint adds --front-env front/.env.prod when that file exists, or says what the flag is for.
  • R12-2: weft target export names each secret it set (never a value).
  • R12-3 timer: a starting copy counts from when the start was asked (setup run or apply command, the earlier of that and its row's stamp), and durations are read on the install's clock (asOfUnix on ApplyProgress and unanswered calls).
  • R12-3 raw error: a running container whose readiness check fails inside its startup window (from the probe: initial delay + period x failure threshold) reads as starting; past it the raw error shows.
  • R12-4: ctx.infra(..).request_start() returns once the start is accepted; StartInstanceInfra gains waitUntilRunning (default on). Docs and Tangle teach start, then reply 202.
  • VS Code extension bumped (graph package changed).

Checked locally: everything CI runs (nextest, doc tests, clippy, parse-only, examples, all db tests, JS checks, docs, terraform validate) and e2e instances + infra stop/cancel.

…ing, let a start finish once accepted, and name what an export sets

- A copy being started counts from when the start was asked (the setup
  run or the apply command), the earlier of that and its row's stamp,
  and the duration is read on the install's clock (ApplyProgress and
  unanswered calls carry as_of_unix), so a reader's clock drift no
  longer shifts it.
- A running container whose readiness check fails within its startup
  window (initial delay plus period times failure threshold, from the
  probe) reads as starting, not as the raw error; past it the raw error
  shows as before.
- ctx.infra(..).request_start() returns once weft accepts the start;
  start() is that plus the wait until running. StartInstanceInfra gains
  waitUntilRunning (default on), so a route can start and then reply 202
  with the copy already listed as provisioning. Docs and Tangle teach
  start, then reply.
- weft target export names each secret it set (never a value), and the
  next-step hint adds --front-env front/.env.prod when that file exists,
  or says what the flag is for.
@qfeuilla
qfeuilla merged commit 36f0c3d into main Oct 8, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant