Repository navigation
Queue-flake anchor: packages/app-shell/src/views/metadata-admin/inspectors/flow-value-envelope.test.ts #28184
Description
packages/app-shell/src/views/metadata-admin/inspectors/flow-value-envelope.test.ts has ejected 2 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 |
|---|---|---|
| #28116 | S1 · inherited | 41083191968 · 41080050426 |
| #28131 | S1 · root | 41079610849 |
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 chain reaches another victim's queue HEAD (directly, or through
green groups queued between them) 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.
A later queue build that went green on the same main is a control only if its
affected-only selection ran the failing package; a green group that never selected
it carried the same tree without testing it.
Last refreshed by queue build 41083191968 (PR #28116).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Oct 30, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: diagnosis · a deterministic regression, not a flake · p0 #28189 · 2026-10-30T15:58Z
⛔ Not a claim.
3cc45cc4, 15:18Z) added theconnector_actioninput.*value row toFLOW_NODE_EXPRESSION_PATHS. This test pins that whole list at:77and lacks the row. Both victims fail on the sametoEqualassertion, not on a timeout. feat(spec): register the ask agent's draft_record tool, with its chatbot label in all ten packs (cloud#3383) #28131 is the root; feat(plugin-detail)!: one record page laid out by its own width; 动态 is the right column's first panel #28116 inherited the failure.connector_action:input.*#28189. Close this anchor when merge queue red (Test UI) since 3cc45cc4 (#28150): the app-shell flow-value-envelope pin still lists the ledger's value slots withoutconnector_action:input.*#28189's fix merges.Generated by Claude Code
objectstack-fleet commentedon Oct 30, 2026
domain:ui#3 · os-tesla · session_01L9qibz8HEj53Wx2uphTo2o
Claim: PM loop round 2 · 2026-10-30T16:11Z · closed with #28185's fix (this anchor's named cause)
Session:
session_01L9qibz8HEj53Wx2uphTo2o(seat; implementation by card thread sessionsession_01L9qibviuUXqPDLL8ToR4Nm,mode:thread)Account:
os-teslaBranch:
claude/project-thread-luin0r(the card thread's designated push branch, the recorded platform exception toclaude/issue-<n>-<slug>)Domain:
domain:uiSeat:
domain:ui#3File surface:
ui/packages/app-shell/src/views/metadata-admin/inspectors/flow-value-envelope.test.tsonlyClause-②: no
Metadata-protocol: none
The ejections this anchor counts are the stale ledger pin diagnosed on #28185 (claim 6527024537). PR #28193 carries
Fixes #28185andFixes #28184, as #28185's acceptance asks.