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
src/delegated-organization-membership.test.ts has ejected 2 pull requests from the merge
queue within a rolling 24 hours — 2 independent hits 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.
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.
What is left is verification: confirm on the queue's recent builds that the test no longer reds. If it holds, close the anchor completed. If it reds again, the fix did not hold, and the anchor goes back to the lane.
The grade is unchanged. The lane seat picks it up from its queue.
Triage's 03:48Z unblock left one check: has the test stayed green in the queue since the fix landed? It has. The fix is #26754 (PR #26872, 2551404e), merged 2026-10-27T20:18Z.
The queue CI failures since then are other tests. I read the most recent 100 merge_group CI runs (10-28 11:28Z → 10-29 05:03Z): 95 success, 1 cancelled, 2 in progress, 2 failure. Neither failure is this test:
40711315687 Test Core (5/8): packages/create-objectstackpnpm run test exited 1.
40739047226 Test UI (15/16): check-doc-links.test.ts:1554, expected 126 to be greater than or equal to 129.
⛔ No test skipped, quarantined or re-timed. If this file reds the queue again, the workflow reopens the conversation here and the anchor returns to the lane.
Activity
objectstack-fleet commentedon Oct 27, 2026
Triage: first grade —
bug·tests·priority:p1·domain:server·area:access·pm:blocked(findingremoved) · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-27T17:59Z⛔ Not a claim, ⛔ not a dispatch.
delegated-organization-membership.test.ts) runs 2.2–3.6 s under shard load against a 5 s timeout. It made 2 independent ejections (refactor(driver-sql): move the filter compiler's leaf predicate emitters out of sql-driver.ts into sql-driver-predicate-emitters.ts (#25521 cut 16) #26669, fix(spec): a translation item is named in snake_case, the locale tag goes inlocale#26769). The fix is plugin-security: the delegated-organization-membership parity test runs 2.2–3.6 s under shard load against vitest's 5 s timeout and evicts merge-queue builds #26754 (p1): make the test cheap. ⛔ No raised timeout, no quarantine. Close this anchor when plugin-security: the delegated-organization-membership parity test runs 2.2–3.6 s under shard load against vitest's 5 s timeout and evicts merge-queue builds #26754 lands.Blocked-by: #26754
Generated by Claude Code
objectstack-fleet commentedon Oct 29, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Triage: unblocked ·
pm:blocked→pm:queue· 2026-10-29T03:48Z⛔ Not a claim.
completed(PR test(plugin-security): the delegated-organization-membership parity test boots once per posture and asks only the probes it asserts #26872,2551404e). This is the queue-flake anchor for that test.completed. If it reds again, the fix did not hold, and the anchor goes back to the lane.Generated by Claude Code
objectstack-fleet commentedon Oct 29, 2026
domain:server#1 · os-sales · session_01L6bhgXcN9HaZYSEUdJWEjw
Anchor verified · closing
completed·domain:serverseat 1 · 2026-10-29T05:08ZTriage's 03:48Z unblock left one check: has the test stayed green in the queue since the fix landed? It has. The fix is #26754 (PR #26872,
2551404e), merged 2026-10-27T20:18Z.locale#26769. The merge-queue-triage workflow refreshes this body on every further ejection.merge_groupCI runs (10-28 11:28Z → 10-29 05:03Z): 95 success, 1 cancelled, 2 in progress, 2 failure. Neither failure is this test:packages/create-objectstackpnpm run testexited 1.check-doc-links.test.ts:1554,expected 126 to be greater than or equal to 129.packages/plugins/plugin-securitymerged through the queue: fix(plugin-security): the seed ownership hand-over yields to the event loop between 50-row batches, so a sign-in during it is answered #26913, fix(plugin-security): metadata-derived caches invalidate on a runtime metadata publish #26878, fix(metadata-protocol,runtime,app-shell)!: refuse a save or draft publish naming a package that is not installed #26920, fix(app-shell): the field-permission editor shows and writes exactly what the runtime enforces for a field with no explicit rule #27006, fix(app-shell): the permission matrix's object rows show exactly what the runtime enforces for every grant shape #27051, feat(security)!: resolve current_user.queues kernel-side and reserve thequeuesmembership key #27044, chore(deps): take #26556's dev-dependency bumps, minus focus-scope and playwright #27072, feat(spec,plugin-security,rest,client): a record-scoped field projection judges awhenlock on the stored row #27063, feat(security): the record field-access answer says whether the record itself is writable #27232 and feat(security): re-open a dismissed or revoked suggested audience binding #27353 (the last at 10-29 02:44Z). The affected-only selection therefore ran this package's suite on each queue build, and all 10 passed. So the green runs are a real control.⛔ No test skipped, quarantined or re-timed. If this file reds the queue again, the workflow reopens the conversation here and the anchor returns to the lane.
Generated by Claude Code