Repository navigation
docs(backlog): the hole sits twelve seconds after the process - #460
Merged
Merged
Conversation
The 206df65 swap served one 503 on / while /api/health held 200 through the same second -- the first non-200 in roughly 42 500 requests measured overnight, and a fourth observation for #304. Converted to wall clock as the rule demands: the red second lands +11.3 to +13.3 s after the serving api process came up, which puts the three solid offsets in a cluster around 12 s rather than three scattered points. It was only visible because the window covered 15.3 s past that moment. The same instrument covered 3.4 s on an earlier swap the same night, and a hole at +12 s is invisible to that remainder -- so #453 is the difference between measuring this defect and not. Also corrected here: the tally's escalation criterion is met for the first time, because this failure falls in the swap rather than at rest. The issue it calls for already exists. Co-Authored-By: Claude Code <noreply@anthropic.com>
G1NG4R
deleted the
docs/the-hole-sits-twelve-seconds-after-the-process
branch
October 17, 2026 05:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backlog only — no code. The first non-200 of the night, and what it cost to see
it.
What it carries
206df65swap served one 503 on/while
/api/healthheld 200 through the same second: 1107 requests per path,1106 × 200 and 1 × 503. The first non-200 in roughly 42 500 requests measured
overnight across six witnessed swaps.
wall-clock, not an index (
elapsed=$(( now - start + 1 )),tools/witness.sh:316), so the red second is pinned to 05:14:37Z ±1 s. Theserving process came up at 05:14:25.711Z, which puts the hole at +11.3 to
+13.3 s after it — and the three solid offsets are now a cluster around
12 s (+11.3…13.3, +12, +12.9) rather than three scattered points. Same shape
as before: a 503 rather than a 404, and only the container serving the page.
covered 15.3 s past the serving process; the
3b990e5swap earlier thesame night covered 3.4 s, because the 30 s tail runs from the twin. A
hole at +12 s is invisible to a 3.4 s remainder, and one of the six windows
would have swallowed this 503. test: the witness tail is measured from the twin, and closes before #304's window #453 is the difference between measuring this
defect and not — argued from last night's own two outcomes.
criterion is "two failures on one path or one that falls in the swap".
This one falls in the swap, so it is met for the first time since H7a — all
six previous failures sat at rest, seven to eighteen minutes away from a swap.
The issue it calls for already exists (bug: a container swap sometimes drops one request, and two samples cannot say how often #304); the sentence below the table no
longer reads "not met", and the docs(backlog): #431 accepted, and the thirteenth swap has no hole #444 case is kept separate so the two do not
contradict.
The observation itself is on #304 with its arithmetic beside it, not only here.
make checkgreen.