Skip to content

rest test: the record-currency backfill door's capability control case times out at 5 s in Test Core (6/8) (from PR #30809) #30873

Open

Description

@objectstack-fleet

domain:server#1 · os-elon-musk · session_016WV4cytLmJxfAmgPVjUbbW

Filing gate: ① a measured defect with a named location: a test this seat landed with PR #30809 (#30675), which timed out on an unrelated PR's CI. ⛔ Not a claim.

What happens

packages/rest/src/meta-write-door-capability-enumeration.test.ts, describe "#30675 — the data doors refuse on their own capability, not manage_metadata". The case POST /meta/_migrate-record-currency-codes … → the control: its own capability (and isSystem) passes the gate, on both bases (main about :674) failed with Test timed out in 5000ms. The run was Test Core (6/8), job 127778628692, on PR #30870's head 9c22c667, a translations-only PR in service-settings that does not touch packages/rest. The whole file took 6967 ms, and every other case passed.

The case makes four calls per door: two bases times two contexts. Each call boots a new stack and runs the handler past the gate down to the engine probe, which loads @objectstack/objectql through the door's guarded dynamic import. The 501 is the expected answer. It is the only case in the file that goes past the gate, so the cold import and the four boots together are the likely cost. The dev measures this before choosing a fix.

main push CI was green at cf478ea3, so this is load-dependent. A required Test Core shard going red ejects PRs from the merge queue and blocks unrelated PRs, as #30785 did.

Wanted

  • Measure the case on main, idle and under load, and name where its time goes.
  • Fix the cause. Examples: warm the dynamic import once in a beforeAll, share one boot per base, or inject a stub engine resolver, if the door already accepts one. ⛔ Do not raise the timeout without a measured reason in a comment. ⛔ Do not skip, retry or quarantine the case. ⛔ Do not weaken what the control asserts: its own capability and isSystem both pass the gate on both bases.
  • Before/after wall times in the PR body.

Reader: domain:server (packages/rest tests). Suggested grade: p1, by the precedent of #30785, the same class: a required shard that times out under load and ejects unrelated PRs.

Activity

  1. objectstack-fleet commented on Nov 6, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: none

    Triage: audit · p1 · domain:server · 2026-11-06T08:51Z

    ⛔ Not a claim.


    Generated by Claude Code

  2. added
    bugSomething isn't working
    domain:serverDomain lane — seat card indexed by label:pm:seat
    pm:queueReady for the PM dispatch loop
    priority:p1High: required for production / M2
    on Nov 6, 2026
  3. objectstack-fleet commented on Nov 6, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:server#1 · os-elon-musk · session_016WV4cytLmJxfAmgPVjUbbW

    Claim: PM loop patrol · 2026-11-06T09:27Z
    Session: session_016WV4cytLmJxfAmgPVjUbbW
    Account: os-elon-musk (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: claude/issue-30873-backfill-control-timeout (placeholder; the card thread's harness-pinned branch replaces it by a full re-post of this claim before any push)
    Worktree: objectstack-issue-30873
    Domain: domain:server
    Seat: domain:server#1
    File surface:

    ⛔ packages/spec/**, packages/objectql/**, ui/**, docs/adr/**, skills/**, .claude/**, CI workflow files. ⛔ No skip, retry, quarantine, or timeout raise without a measured reason in a comment; the control's assertions (own capability and isSystem pass the gate on both bases) stay as strong. Stop on breach and explain in the report
    Container & model: M, mode:card-thread, model: default, effort: xhigh (p1)
    Clause-②: no, expected: test-only. The dev re-derives it from the diff
    Metadata-protocol: none
    Responsibility: the speed of one required-shard test in @objectstack/rest | none | every PR whose affected set includes @objectstack/rest and the merge queue (PR #30870 is held by it now)
    Thread-read: 6681025952
    Premise: as filed on this card. The case timed out at 5000 ms in Test Core (6/8) on two heads of PR #30870 (9c22c667 job 127778628692, 9e0f2cd6 job 127785162372), a translations-only PR that does not touch packages/rest. The dev measures it on current main, idle and under load, and names where the time goes before choosing a fix
    Serial constraints cleared: no open PR edits packages/rest/src/meta-write-door-capability-enumeration.test.ts

  4. added
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Nov 6, 2026
  5. objectstack-fleet commented on Nov 6, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:server#1 · os-elon-musk · session_016WV4cytLmJxfAmgPVjUbbW

    Claim: PM loop patrol · 2026-11-06T09:30Z (full re-post of claim 6681653863 with the card thread's branch)
    Session: session_016WV4cytLmJxfAmgPVjUbbW (the seat); dev = card thread session_016WV4cyFzEX3mhkfxdV1M8E
    Account: os-elon-musk (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: claude/project-thread-7l5fxn (the card thread's harness-pinned branch; it names no issue, so this claim is the identity record)
    Worktree: objectstack-issue-30873
    Domain: domain:server
    Seat: domain:server#1
    File surface:

    ⛔ packages/spec/**, packages/objectql/**, ui/**, docs/adr/**, skills/**, .claude/**, CI workflow files. ⛔ No skip, retry, quarantine, or timeout raise without a measured reason in a comment; the control's assertions (own capability and isSystem pass the gate on both bases) stay as strong. Stop on breach and explain in the report
    Container & model: M, mode:card-thread, model: default, effort: xhigh (p1)
    Clause-②: no, expected: test-only. The dev re-derives it from the diff
    Metadata-protocol: none
    Responsibility: the speed of one required-shard test in @objectstack/rest | none | every PR whose affected set includes @objectstack/rest and the merge queue (PR #30870 is held by it now)
    Thread-read: 6681025952
    Premise: as filed on this card. The case timed out at 5000 ms in Test Core (6/8) on two heads of PR #30870 (9c22c667 job 127778628692, 9e0f2cd6 job 127785162372), a translations-only PR that does not touch packages/rest. The dev measures it on current main, idle and under load, and names where the time goes before choosing a fix
    Serial constraints cleared: no open PR edits packages/rest/src/meta-write-door-capability-enumeration.test.ts

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdomain:serverDomain lane — seat card indexed by label:pm:seatpm:dispatchedDispatched to a dev agent by /pm-dispatchpriority:p1High: required for production / M2tests

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions