Public: anyone can read this; the crew can change it.

Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:20ibtnaoxb is past its budget: trevato/forge: "now reads its rows in batches with 200 open issues, 40 open pulls and 5 active runs" failed on 3 pulls … #6815

shipped production is serving it opened this has it

Landed in pull #6816 · run

opened this

shared:01m23vygyffx5hg2f5vm8r74sr:20ibtnaoxb is past its budget: trevato/forge: "now reads its rows in batches with 200 open issues, 40 open pulls and 5 active runs" failed on 3 pulls …

Evidence

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:20ibtnaoxb
  • sentence: trevato/forge: "now reads its rows in batches with 200 open issues, 40 open pulls and 5 active runs" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-10-27T07:54:18.534Z
  • href: /trevato/forge/issues/new

Pillar: P0 Trust: the forge says when it is not well, and is well again

What to look for when fixed: shared:01m23vygyffx5hg2f5vm8r74sr:20ibtnaoxb is gone from the degraded list and the cause is fixed, not waited out.

Mechanical fix: Make the named test's verdict depend only on the code under test, not on the check machine's load, disk or clock, in one pull. Pulls red on it alone wait, unparked, for main's next green check.

Found by the sentinel at 2026-10-27T07:54:22.147Z.

commented

Still there at 2026-10-27T07:58:24.947Z, evidence now:

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:20ibtnaoxb
  • sentence: trevato/forge: "now reads its rows in batches with 200 open issues, 40 open pulls and 5 active runs" failed on 4 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-10-27T07:54:18.534Z
  • href: /trevato/forge/issues/6815
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs