Repository navigation
Queue-flake anchor: src/engine-insert-static-readonly-strip.test.ts #21705
Description
Activity
Triage: first grade —
tests·priority:p2·domain:engine·pm:blocked(findingremoved;queue-flake-anchorstays)Blocked-by: #21682
Triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-04T08:56Z. ⛔ Not a claim, ⛔ not a dispatch.Diagnosis: this is not a flake. The queue's own triage comment carries the failure REASON, an assertion on product behaviour:
the platform's value reaches the driver: expected undefined to be 'stamp'. The cause is a deterministic semantic conflict, local to PR #21701:- The failing case is PR fix(objectql): droppedFields on a create names only keys the caller sent, never a middleware fill (#21682) #21701's own new pin ("[[finding] On a walled posture a create that names no organization_id answers droppedFields [organization_id: readonly], a field the caller never sent (the insert analogue of #8093) #21682] a write middleware's fill is not caller-supplied"). It does not exist on
main, somainis not red on it. - Root: PR fix(objectql)!: a system write's readonly value is judged for its shape — a seed's malformed readonly datetime is refused, never stored (#21663) #21695 (
8843505d91, A system-context write skips value-shape validation for readonly fields: a seed's malformed readonly datetime ('yesterday', an unresolvedcelenvelope) is stored verbatim, while the same value on a non-readonly field is refused #21663) landed onmainwhile PR fix(objectql): droppedFields on a create names only keys the caller sent, never a middleware fill (#21682) #21701 was queued. It judges every readonly value left on an insert row for its shape. The pin's fill of a readonly datetime was the non-date string'stamp', which that check now refuses, so the value never reaches the driver. - PR docs(spec): re-anchor the dead tracker citations in packages/spec/src's test surface to the commits that decided them #21700 was a bystander (
S1 · inherited), as its owning seat recorded (5978020396). It has since merged as7e0066af7a.
The fix is already on PR #21701. Its holder pushed
b7d2799c8d, which fills a valid ISO-8601 instant and leaves what the pin proves unchanged. PR-side checks on that head are green so far (29 success, 1 pending), read in this round. ⛔ Not quarantined; the test is right.This card closes when PR #21701 lands green through the queue. The unlock scan closes it then rather than queueing it. If this signature appears again after that, it is a new hit.
Not this card: the
Console Pin Gatered in the same queue builds is a separate signature, filed as #21709 (a substring collision in the gate's staleness leg, not a leaked spec).
Generated by Claude Code
- The failing case is PR fix(objectql): droppedFields on a create names only keys the caller sent, never a middleware fill (#21682) #21701's own new pin ("[[finding] On a walled posture a create that names no organization_id answers droppedFields [organization_id: readonly], a field the caller never sent (the insert analogue of #8093) #21682] a write middleware's fill is not caller-supplied"). It does not exist on
Closed by the triage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-04T09:57Z, as the grade5978301211set out: this card closes when PR #21701 lands green through the queue.- PR fix(objectql): droppedFields on a create names only keys the caller sent, never a middleware fill (#21682) #21701 merged as
5259a35e69, which closed [finding] On a walled posture a create that names no organization_id answers droppedFields [organization_id: readonly], a field the caller never sent (the insert analogue of #8093) #21682. - Its queue build
37191123449ran everyTest Coreshard green. That includesengine-insert-static-readonly-strip.test.ts, whose middleware-fill pin now fills a valid instant. - The build's only red was
Console Pin Gate. That is ci(console): the Console Pin Gate's staleness leg matches objectui's own ganttmarkersdescription as "the published spec", so every merge-queue build since #21699 is red #21709's substring collision, not this signature. The same holds for the next queue build (37192205626, PR docs(spec): JobSchema.body's describe says an enabled pull job installs when its pull binds and is refused when it does not #21708). - The test was never quarantined, and it is right. If this signature appears again after
5259a35e69, it is a new hit.
Generated by Claude Code
- PR fix(objectql): droppedFields on a create names only keys the caller sent, never a middleware fill (#21682) #21701 merged as
src/engine-insert-static-readonly-strip.test.tshas ejected 2 pull requests from the mergequeue 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.
stackcolumn is read out of the queuebranch 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
inheritedrow 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 37186683796 (PR #21700).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).