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

Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1sq3qvly0n is past its budget: trevato/forge: "a forge snapshotted again and again > another passphrase reads nothing, and no name on the bucket is th… #12628

shipped production is serving it opened this has it

Landed in pull #12629

opened this

shared:01m23vygyffx5hg2f5vm8r74sr:1sq3qvly0n is past its budget: trevato/forge: "a forge snapshotted again and again > another passphrase reads nothing, and no name on the bucket is th…

Evidence

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:1sq3qvly0n
  • sentence: trevato/forge: "a forge snapshotted again and again > another passphrase reads nothing, and no name on the bucket is the hash of any plaintext" failed on 6 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-11-14T17:05:58.488Z
  • href: /trevato/forge/issues/new
  • test: a forge snapshotted again and again > another passphrase reads nothing, and no name on the bucket is the hash of any plaintext
  • failed: pull #12498, check run 01m7dcxbts81zp1gjg287qwhg5
  • failed: pull #12605, check run 01m7dcx0vh770gbx3b32xfhj21
  • failed: pull #12590, check run 01m7dcw90ahwjfwamjc3trj9kz
  • failed: pull #12603, check run 01m7dctm78mnapxqhv75qrpfp6
  • failed: pull #12600, check run 01m7dbh7aewzar1z6yqxjkarhx
  • base: [redacted] (run 01m7dcxbts81zp1gjg287qwhg5)
  • log: 182 | } catch (error) {
  • log: 183 | last = error;
  • log: 184 | if (n + 1 < attempts) await sleep(baseMs * 2 ** n);
  • log: 185 | }
  • log: 186 | }
  • log: 187 | throw new Error(
  • log: ^
  • log: error: get sealed/lane.json failed after 1 attempt: an unexpected error has occurred
  • log: at tried (src/snapshot/store.ts:187:15)
  • log: at async laneKeys (src/snapshot/sealed_store.ts:83:28)
  • main: passes on main's newest check, run 01m7dg6r9aqdnk644bgydtst6z 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:1sq3qvly0n 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-14T17:06:08.402Z.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs