Issues

status reports elapsed_s and the current resource for an in-progress apply

#587

· noahgift opened

on Sep 16, 2026

a drift/check/apply verdict never names the lock it read — three locks for one machine gave three answers and the output could not tell them apart

bug

#585

· noahgift opened

on Sep 16, 2026

·

1.32.0

drift calls a file DRIFTED when its live content matches the declaration byte-for-byte — five for five on one host, because it compares against a four-week-old lock

#584

· noahgift opened

on Sep 16, 2026

drift with a missing state dir inspected 40 of 153 and still returned 'Drift detected: 2' — one host and one commit produced 2, 3 and 9 across three sessions

#582

· noahgift opened

on Sep 16, 2026

remote resources have no content key — an SSH target plans NoOp over changed sources, and infra has 35 hand-rolled activation checks standing in for it

#581

· noahgift opened

on Sep 16, 2026

apply/plan should refuse when the running binary != the forjar version the manifest pins (four infra hosts applied for months under a 1.25.2/1.27.0 parser)

#579

· noahgift opened

on Sep 16, 2026

release goal: RED — GATE T FAIL v1.31.0 is reachable from HEAD, at or above the floor v1.25.0, and h

release-goal

#578

· github-actions opened

on Sep 16, 2026

quorum receipt reports STALE for a correct receipt on some runners; the same head passes on rerun — the gate prints nothing to diagnose it

bug

#573

· noahgift opened

on Sep 15, 2026

·

1.32.0

quorum.yml's receipt job builds against the shared ~/.cargo — the fleet test cannot see cargo run through a script

bug

#572

· noahgift opened

on Sep 15, 2026

·

1.32.0

lint.yml on the fleet: a clean-room runner has no cargo-clippy for the 1.89 toolchain — first fleet run of lint after PMAT-547

bug

#567

· noahgift opened

on Sep 15, 2026

·

1.32.0

mutation.yml: cargo install cargo-mutants pulls deps that need rustc 1.91 on the fleet's 1.89 toolchain — red on main since 2026-09-14

bug

#566

· noahgift opened

on Sep 15, 2026

·

1.32.0

lock keyed by (machine, stack), host-resident; apply refuses a manifest-sha mismatch without --adopt; generator field records the real writer

#561

· noahgift opened

on Sep 15, 2026

·

1.32.0

Navigation Menu

Uh oh!

All issues

status reports elapsed_s and the current resource for an in-progress apply

a drift/check/apply verdict never names the lock it read — three locks for one machine gave three answers and the output could not tell them apart

drift calls a file DRIFTED when its live content matches the declaration byte-for-byte — five for five on one host, because it compares against a four-week-old lock

drift with a missing state dir inspected 40 of 153 and still returned 'Drift detected: 2' — one host and one commit produced 2, 3 and 9 across three sessions

remote resources have no content key — an SSH target plans NoOp over changed sources, and infra has 35 hand-rolled activation checks standing in for it

apply/plan should refuse when the running binary != the forjar version the manifest pins (four infra hosts applied for months under a 1.25.2/1.27.0 parser)

release goal: RED — GATE T FAIL v1.31.0 is reachable from HEAD, at or above the floor v1.25.0, and h

quorum receipt reports STALE for a correct receipt on some runners; the same head passes on rerun — the gate prints nothing to diagnose it

quorum.yml's receipt job builds against the shared ~/.cargo — the fleet test cannot see cargo run through a script

lint.yml on the fleet: a clean-room runner has no cargo-clippy for the 1.89 toolchain — first fleet run of lint after PMAT-547

mutation.yml: cargo install cargo-mutants pulls deps that need rustc 1.91 on the fleet's 1.89 toolchain — red on main since 2026-09-14

lock keyed by (machine, stack), host-resident; apply refuses a manifest-sha mismatch without --adopt; generator field records the real writer

Uh oh!

Search results