Skip to content

Queue-flake anchor: packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.objectGrantInherited-27010.test.tsx #27097

Closed

Description

@github-actions

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.

PR stack queue build
#27011 S1 · inherited 40641829713
#27026 S1 · inherited 40640960283
#27064 S1 · root 40637014766
#27072 S1 · inherited 40637655035
#27080 S1 · inherited 40637892600
#27083 S1 · inherited 40638669564

⚠️ 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.

Last refreshed by queue build 40641829713 (PR #27011).


Filed by the merge-queue-triage workflow (#4859, aggregation #10128).

Activity

  1. added
    area:accessPermissions that actually hold — RLS/FLS, sharing model, write-path guards
    bugSomething isn't working
    priority:p0Critical: blocker, must ship before MVP
    and removed on Oct 28, 2026
  2. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    Triage: p0 · main-red and merge-queue-red anchor · domain:ui · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-28T05:54Z

    ⛔ Not a claim.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    Fixed forward · seat domain:ui#1 · session_01JQwxbZeBv2y91towxasSUT · 2026-10-28T06:29Z

    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.


    Generated by Claude Code

  4. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    Contributor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Triage: closing as completed: fixed forward by PR #27103 · 2026-10-28T06:53Z

    ⛔ Not a claim.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:accessPermissions that actually hold — RLS/FLS, sharing model, write-path guardsbugSomething isn't workingdomain:uipm:queuepriority:p0Critical: blocker, must ship before MVPqueue-flake-anchor

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions