Repository navigation
Queue-flake anchor: src/__tests__/caller-content-admission-door.test.ts #21200
Description
src/__tests__/caller-content-admission-door.test.ts has ejected 4 pull requests from the merge
queue within a rolling 24 hours — 1 independent hit once
GitHub's speculative stacking is accounted for. This issue is the single place for
that conversation; it is refreshed by the merge-queue-triage workflow on every
further ejection.
| PR | stack | queue build |
|---|---|---|
| #21188 | S1 · inherited | 36885837931 |
| #21190 | S1 · root | 36885164397 |
| #21192 | S1 · inherited | 36889153084 |
| #21195 | S1 · inherited | 36889082281 |
stack column is read out of the queue
branch names: GitHub builds each queued PR on top of the previous entry, so a
build whose BASE commit IS another victim's queue HEAD contains that victim's
tree by construction. A single deterministic break therefore ejects every PR
behind it, and the raw victim count climbs with QUEUE DEPTH until the owner
lands a fix. Start with the root above; an inherited row is a bystander until shown otherwise.
This issue is a NAME, not a diagnosis. The workflow that files it reads the
failing test file path out of the job logs and counts PRs; it does not
know whether this is a flake, a load/timing cliff, a semantic conflict between
queued PRs, or a real regression, and it does not act on any of those. No test is
skipped, quarantined or re-queued by it, and no PR is labelled by it — weakening
a gate stays a human act.
What to do with it: read one victim PR's triage comment for the failure REASON
line beside the FAIL line (a timeout and an assertion are the same FAIL line and
opposite diagnoses), decide the cause, and close this issue with the fix or with
the reason it is not one.
Last refreshed by queue build 36889082281 (PR #21195).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Oct 1, 2026
Triage: route —
priority:p1·domain:services·area:reports·pm:queue. One incident, two anchors. The root is PR #21190, the fix for #21177 (p0)Triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-01T16:54Z. ⛔ Not a claim, ⛔ not a dispatch.Fixes #21177,service-analytics), the row markedrootin the table. The threeinheritedrows all merged at 2026-10-01T16:38Z (read at this write).Generated by Claude Code
objectstack-fleet commentedon Oct 1, 2026
Triage: closed
completed. The cause was decided and fixed, and the root landedTriage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-01T19:00Z. This anchor closes on its own condition: "decide the cause, and close this issue with the fix or with the reason it is not one".5936800470): a semantic overlap, not a flake.mainthat refuses the same members with a different code.main. PR fix(service-analytics)!: refuse a caller-supplied analytics member that is not a column reference at the door #21190 then merged through the queue asce4e205e2b, and [security] An analytics query surface evaluates caller-supplied content outside the object- and field-level read admission, so a non-admin member can read data they are refused everywhere else — detail withheld pending maintainer #21177 is closedcompleted.inheritedrows were bystanders, and they merged earlier.Generated by Claude Code