Skip to content

analog: linear_zoh.t27 -- rename struct Ring to RingPeak, it collided with another type named Ring and moved the types ratchet 107 -> 108 (Closes #10503) - #10539

Merged
gHashTag merged 1 commit into
masterfrom
claude/analog-m1c-ring-rename-10503
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
claude/analog-m1c-ring-rename-10503

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10503

Follow-up to #10528 (M1c, specs/analog/linear_zoh.t27), which merged with a defect that its own gates did not catch.

What went wrong

#10528 declared pub struct Ring for the tank test. The corpus-ratchet job runs tri types ratchet, and on that PR it failed: ledger 107 name(s), observed 108, + Ring NEW conflict, i.e. a type name with two definitions in the corpus. The job is not a required check, so auto-merge went through and master is now red on it (master's run at the base commit 1d8477c was green). I had run test-report, tri test, seal --verify and dupe_scan locally, but not tri types ratchet.

Fix

Rename the struct Ring to RingPeak (no other definition of that name exists). Nothing else changes: 2 files, 14 lines each way (the struct, its two return types, two constructors, three const ... : RingPeak in the tank test, plus the re-saved seal).

Evidence

Left as it is

🤖 Generated with Claude Code

… with another type named Ring and moved the types ratchet 107 -> 108 (Closes #10503)

PR #10528 merged specs/analog/linear_zoh.t27 with `pub struct Ring`. The
corpus-ratchet job ran `tri types ratchet` and failed: ledger 107 names,
observed 108, "+ Ring NEW conflict" -- a type name with two definitions in the
corpus. The job is not a required check, so the merge went through; master is
red on it until this lands.

The struct holds the peak amplitude of the scheme and the analytic one in the
tank test. Renamed to RingPeak (no other definition of that name). Nothing
else changes: the same 15 tests pass with 0 vacuous, the seal is re-saved
(15/15), `tri types ratchet` is CLEAN at 107/107, dupe_scan says ok.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 17:10:53 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 44
PRs with All Checks Green 6
READY 0
FAILING 44
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 44 + 0 + 0 = 44, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != 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).

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.

analog M1c: exact zero-order-hold discretization for the linear cell, and the h / h/2 convergence check

2 participants