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

Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2kakdc4hcr is past its budget: trevato/forge: "the ping is signed and goes through deliverDue, body { kind, repo, hook, at }" failed on 3 pulls in the… #12509

shipped production is serving it opened this has it

Landed in pull #12510 · 2 runs · run

opened this

shared:01m23vygyffx5hg2f5vm8r74sr:2kakdc4hcr is past its budget: trevato/forge: "the ping is signed and goes through deliverDue, body { kind, repo, hook, at }" failed on 3 pulls in the…

Evidence

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:2kakdc4hcr
  • sentence: trevato/forge: "the ping is signed and goes through deliverDue, body { kind, repo, hook, at }" 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-11-14T11:02:35.356Z
  • href: /trevato/forge/issues/new
  • test: the ping is signed and goes through deliverDue, body { kind, repo, hook, at }
  • failed: pull #12429, check run 01m7csrqnsm4atknxg79zf8rt9
  • failed: pull #12438, check run 01m7cqs91qvfgmw37kf8jc8e9f
  • failed: pull #12312, check run 01m7cm9tt3j52f9vtc18q7e142
  • base: [redacted] (run 01m7csrqnsm4atknxg79zf8rt9)
  • log: 109 |
  • log: 110 | test("the ping is signed and goes through deliverDue, body { kind, repo, hook, at }", async () => {
  • log: 111 | received = [];
  • log: 112 | app.db.run("UPDATE webhook SET url = ?2 WHERE id = ?1", [hookA, http://127.0.0.1:${receiver.port}/h]);
  • log: 113 | await deliverDue(app.db, app.log, new Date(), LOOPBACK);
  • log: 114 | expect(received).toHaveLength(1);
  • log: ^
  • log: error: expect(received).toHaveLength(expected)
  • log: Expected length: 1
  • log: Received length: 0
  • log: at <anonymous> (test/hook-ping.test.ts:114:20)
  • main: passes on main's newest check, run 01m7bhyf02fje76g09qbmmhtsp at [redacted]

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

What to look for when fixed: shared:01m23vygyffx5hg2f5vm8r74sr:2kakdc4hcr 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-11-14T11:03:14.700Z.

commented

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs