Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   priority:p1High: required for production / M2High: required for production / M2

   domain:devx

   on Oct 5, 2026
2. objectstack-fleet commented on Oct 5, 2026

   

   objectstack-fleetbot

   on Oct 5, 2026

   Contributor

   More actions

   Path: fleet decision — the hourly full run says whether the whole tree is green (#16467) | 缺项 | none

   Triage: routed — pm:on-hold. The red is the third timeout of one test, and that test now has its own card: #21920 (bug · priority:p1 · domain:devx stay as the generator filed them)

   Restart-when: the next scheduled CI run on main after e6dc7a2406 concludes. If it is green, this card closes, and the timing work stays on #21920. If it is red on the same case with Test timed out, this card closes against #21920, which already owns that case. If it is red on anything else, triage re-reads it.

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-05T23:56Z. ⛔ Not a claim, ⛔ not a dispatch.

   Triage: lands in packages/rest/src/meta-state-route-engine-outage.test.ts (:296) ⇒ the work is on #21920 in domain:cli; rationale: this card is the generator's signal, and a work card must not have its body rewritten on the next red.

   What the run shows (run 37386040871, at e6dc7a2406):

   • Test Core (5/6) had one failure: the [#15405] §0 multi-kernel wiring case, Test timed out in 5000ms. The other 4,897 tests in @objectstack/rest passed.
   • The range holds one commit, fix(metadata-core,rest,runtime): judge an objectOverride action param against the object it names #21904 (objectOverride action params). Its rest-server.ts change is on the object-schema mask path, not the state route this case drives. The same case timed out the same way on hourly full run: red on main (CI) #21757 and hourly full run: red on main (CI) #21778, before that commit existed, so the commit is not the reading here.

   This amends my close of #21778. That was the second timeout of this same case, and #21757's Restart-when: already said a repeat becomes the test's timing card. I closed it not_planned instead. #21920 is that card, filed now with all three occurrences.

   ---

   Generated by Claude Code
3. objectstack-fleet

   added

   pm:on-hold

   on Oct 5, 2026
4. objectstack-fleet commented on Oct 6, 2026

   

   objectstack-fleetbot

   on Oct 6, 2026

   Contributor

   More actions

   Closed by the triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-06T00:58Z, on the hold's Restart-when: (6005911233): the next scheduled CI run on main after e6dc7a2406 concluded green.

   • Run 37391844594 at 833d57c9cf, which contains e6dc7a2406, concluded success.
   • The red's only failure was the third Test timed out in 5000ms of meta-state-route-engine-outage.test.ts:296. That case's timing is owned by test(rest): meta-state-route-engine-outage.test.ts's multi-kernel wiring case times out at vitest's 5000 ms default under the hourly full run, and has turned main's hourly run red three times in two days #21920 (domain:cli, now pm:dispatched), which keeps all three occurrences. This green run does not close it.
   • ⛔ No check was narrowed or skipped. If a later hourly run times out on the same case, it belongs to test(rest): meta-state-route-engine-outage.test.ts's multi-kernel wiring case times out at vitest's 5000 ms default under the hourly full run, and has turned main's hourly run red three times in two days #21920. Anything else, the generator files fresh.

   ---

   Generated by Claude Code
5. objectstack-fleet

   removed

   pm:on-hold

   on Oct 6, 2026
6. objectstack-fleet

   closed this as completedon Oct 6, 2026