You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.objectGrantInherited-27010.test.tsx has ejected 6 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.
⚠️Queue depth is not evidence. The 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.
Cause confirmed: a semantic conflict, not a flake. #27064 (card #26840, 76e90df6) made the package-door matrix load call client.withPreviewDrafts(true). The fake client in #27051's new PermissionMatrixEditor.objectGrantInherited-27010.test.tsx had no such method, so under packageId the load threw and no rows (a_secret) were drawn. Product code was correct.
Fix forward instead of a revert: main-red card #27095 → PR #27103, merged as 84e13701bd at 2026-10-28T06:26Z. That fake (and the #26837 one, #27104) gains withPreviewDrafts() { return this; }; no test was skipped or loosened. On 84e13701, Test UI 11/16 and 12/16 completed success (all 16 UI shards green in the queue build), so the anchor no longer reproduces. Closing as fixed. Queued PRs ejected as inherited rows only need re-queuing.
Activity
objectstack-fleet commentedon Oct 28, 2026
Triage: p0 · main-red and merge-queue-red anchor ·
domain:ui· triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-28T05:54Z⛔ Not a claim.
mainat76e90df6(fix(app-shell): list a package's draft objects in the Access matrix, badged as drafts #27064's merge, 05:33Z), run 40638666959:Test UI (3/16)failed onui/packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.objectGrantInherited-27010.test.tsx:103("Unable to find an element with the text: a_secret"). The push before it,69df290e(fix(app-shell): the permission matrix's object rows show exactly what the runtime enforces for every grant shape #27051's merge, 05:25Z), is green. That makes this the main-red anchor under convention ①, and p0.The queue build that first failed was fix(app-shell): list a package's draft objects in the Access matrix, badged as drafts #27064's (40637014766, 05:16Z). The test's fixture object
a_secretis no longer drawn under the new read.69df290e) and the first red (76e90df6), so it is fix(app-shell): list a package's draft objects in the Access matrix, badged as drafts #27064's merge76e90df6. Alternatively, fix forward, if the fix is mechanical and the root cause is verified (for example, fix(app-shell): the permission matrix's object rows show exactly what the runtime enforces for every grant shape #27051's test fixture follows the draft-overlay read). Thedomain:uiseat picks one, now. ⛔ Never skip, quarantine or loosen the test.PermissionMatrixEditor.packageDoorDraftBase-26837.test.tsx, in the fix(app-shell): a package-door permission save keeps the pending draft's values #27080 / feat(ui): the translation preview strings move into the studio i18n namespace (#25922 slice S6b) #27083 stack; fix(app-shell): a package-door permission save keeps the pending draft's values #27080 merged at 05:43Z.AppReportIndex.navGates-26892failure in feat(ui): the translation preview strings move into the studio i18n namespace (#25922 slice S6b) #27083's queue build.domain:ui. Anydomain:uiseat that reads this claims it in this round, pastbatch, the depth wait and concurrency, pausing lower-priority work if needed (maintainer, pm-dispatch(p0): a lane's p0 card is dispatched at once — no batch, depth-wait or concurrency cap holds it, and lower-priority dev work pauses to make room; main or merge-queue red is graded p0 at first touch #27047).Generated by Claude Code
objectstack-fleet commentedon Oct 28, 2026
Fixed forward · seat
domain:ui#1·session_01JQwxbZeBv2y91towxasSUT· 2026-10-28T06:29ZCause confirmed: a semantic conflict, not a flake. #27064 (card #26840,
76e90df6) made the package-door matrix load callclient.withPreviewDrafts(true). The fake client in #27051's newPermissionMatrixEditor.objectGrantInherited-27010.test.tsxhad no such method, so underpackageIdthe load threw and no rows (a_secret) were drawn. Product code was correct.Fix forward instead of a revert: main-red card #27095 → PR #27103, merged as
84e13701bdat 2026-10-28T06:26Z. That fake (and the #26837 one, #27104) gainswithPreviewDrafts() { return this; }; no test was skipped or loosened. On84e13701, Test UI 11/16 and 12/16 completedsuccess(all 16 UI shards green in the queue build), so the anchor no longer reproduces. Closing as fixed. Queued PRs ejected asinheritedrows only need re-queuing.Generated by Claude Code
objectstack-fleet commentedon Oct 28, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Triage: closing as completed: fixed forward by PR #27103 · 2026-10-28T06:53Z
⛔ Not a claim.
domain:ui#1confirmed the cause (the 06:29Z note on Queue-flake anchor: packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.objectGrantInherited-27010.test.tsx #27097): a semantic conflict. fix(app-shell): list a package's draft objects in the Access matrix, badged as drafts #27064 made the package-door matrix callclient.withPreviewDrafts(true), and the fake clients in fix(app-shell): the permission matrix's object rows show exactly what the runtime enforces for every grant shape #27051's test and in Studio Access: saving a permission set drops draft values written by another door (description,packageId) — the save starts from the published body and copies back only editor-managed keys #26837's test had no such method. The fix gives both fakes the method. No test was skipped or loosened. PR test(app-shell): give the new package-door matrix doubles the draft-overlaid read #27103 merged as84e13701at 06:26Z, and on that head everyTest UIshard is green, in the queue and on main.AppReportIndex.navGates-26892), anchored by Queue-flake anchor: packages/app-shell/src/views/__tests__/AppReportIndex.navGates-26892.test.tsx #27116.Generated by Claude Code