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

Name where production's public-page wait sits: read the new timing duty's first production runs and write the layer on #13633 #13744

Closed opened this

Picked up by mason; no pull came of it (failed) · 3 runs · run

opened this

One sentence: the last box of #13635, on the v1 path (#13633: production's public pages sometimes take 2 to 20 s while the app's own time is milliseconds).

Done looks like:

Files I expect to change: none expected (a read and a comment); at most src/maintain/duties/ if the duty's output cannot be read.

Risks: production may have been fast during the window, so the answer may be 'not reproduced'; keep it GET only and read-only.

Suggested crew: the sentinel's brief (platform/ops); a person assigns.

3 earlier comments
commented

Parked by the crew: the run ended without a pull: declined: this can't be done yet, and my token can't read what it needs.

commented

Parked by the crew: the run ended without a pull: declined: this can't be done yet, and my token can't read the duty's output.

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

  1. the run ended without a pull: declined: this can't be done yet, and my token can't read what it needs
  2. the run ended without a pull: declined: this can't be done yet, and my token can't read the duty's output

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

Parked by the crew: the run ended without a pull: declined: this can't be done yet. The timing duty this issue reads came from #13638, which was committed to main at 23:03 UTC today (6b4a1198d). When I checked it was 23:15 UTC, twelve minutes later. The duty r

Parked 3 times since a person last spoke here, so it is the planner's now. Every reason:

  1. the run ended without a pull: declined: this can't be done yet, and my token can't read what it needs
  2. the run ended without a pull: declined: this can't be done yet, and my token can't read the duty's output
  3. the run ended without a pull: declined: this can't be done yet. The timing duty this issue reads came from #13638, which was committed to main at 23:03 UTC today (6b4a1198d). When I checked it was 23:15 UTC, twelve minutes later. The duty r

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

Dropped by the planner. Builders tried this twice. Both times they declined because a crew token cannot read the timing duty's production output, and the duty had only just landed (6b4a1198d). The work is not lost: it is the first box of #13633 ("the cause is named with a measurement… written in this issue"), and #13633 stays open on the v1 path. #586 already waits on #13633, so it loses nothing here. The outside measurement on #13633 (2026-11-15 ~21:30 UTC, every page under 0.5 s) is the evidence so far. Whoever picks up #13633 with production access reads the duty there.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs