Skip to content

feat(tri): cache mutation rows so the full run can be finished (#2492) - #2533

Merged
gHashTag merged 3 commits into
masterfrom
feat/mutate-cache
Aug 23, 2026
Merged

gHashTag merged 3 commits into
masterfrom
feat/mutate-cache

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Five operators over 21 gates passed twenty minutes and kept growing — gft_backprop_microcode.py alone has 47 sites, each a ten-second subprocess. The last two attempts were killed by timeouts, and one of those kills is what leaked two mutants into a branch (#2530).

The cost had stopped being an inconvenience and started being a correctness problem: the full picture was the entire point of --all, and nobody could reach it.

Cached by what the answer depends on

The gate's bytes and the bytes of whatever control judges it. Both hashed, both must match.

The cache is written after every gate rather than at the end, so an interrupted run keeps what it measured and the next one resumes. Cold 2.6s → warm 0.5s on one gate.

Every reused row says [cached]

A cached green that read like a fresh one would be precisely the lie this command exists to find. The summary names the split: N measured, M reused.

I put that marker into one of two print paths, then two of three. The multi-column branch got it first; the single-operator branch printed cached rows identically to fresh ones; and the zero-site branch — "no failure path to break" — printed a third way with no marker at all. Three printers, one property, two corrections to reach all three. The same shape as skip() in four copies, inside one function.

Invalidation is verified, not assumed

On a planted repository: measure, reuse, then append one comment to the gate and watch the third run measure again. A cache that never invalidates is worse than no cache, and that direction is the one worth testing.

The stale case, stated rather than hidden

A fixture changing underneath a gate and its control leaves both hashes intact and the recorded row wrong. That is why the marker exists instead of silence: a reader who sees [cached] knows which question to ask, and --fresh answers it.

Refs #2492

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 11:40:39 UTC

Summary

Status Count
Total Open PRs 7
PRs with Failing Checks 3
PRs with All Checks Green 4
READY 3
FAILING 3
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit c43035d into master Aug 23, 2026
22 of 24 checks passed
@gHashTag
gHashTag deleted the feat/mutate-cache branch August 23, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant