Render sweep-boundary KindMismatch/MissingKnob as prose, not Debug structs #247

Closed
opened 2026-07-13 04:50:21 +02:00 by Brummel · 0 comments
Owner

Two sweep-boundary errors on the blueprint verb path print raw Rust Debug structs where the neighbouring diagnostics ship prose (found by the #246 per-cycle fieldtest, evidence fieldtests/cycle-246-bound-override/bo_transcript.txt):

aura: KindMismatch { name: "sma_signal.fast.length", expected: I64, got: F64 }
aura: MissingKnob("sma_signal.slow.length")

beside the polished sibling on the same verb:

aura: axis sma_signal.nope: names no param of this blueprint (open or bound) — see `aura sweep <bp> --list-axes`

Both come from the sweep terminal's BindError rendered via {:?} at the IO wrapper (crates/aura-cli/src/main.rs, blueprint_sweep_family's map_err). Expected: prose of the same register as the unknown-axis message — name the axis, the expected vs supplied kind (or the unbound knob), and point at --list-axes. Exit codes are already correct (2).

Two sweep-boundary errors on the blueprint verb path print raw Rust Debug structs where the neighbouring diagnostics ship prose (found by the #246 per-cycle fieldtest, evidence fieldtests/cycle-246-bound-override/bo_transcript.txt): ``` aura: KindMismatch { name: "sma_signal.fast.length", expected: I64, got: F64 } aura: MissingKnob("sma_signal.slow.length") ``` beside the polished sibling on the same verb: ``` aura: axis sma_signal.nope: names no param of this blueprint (open or bound) — see `aura sweep <bp> --list-axes` ``` Both come from the sweep terminal's BindError rendered via {:?} at the IO wrapper (crates/aura-cli/src/main.rs, blueprint_sweep_family's map_err). Expected: prose of the same register as the unknown-axis message — name the axis, the expected vs supplied kind (or the unbound knob), and point at --list-axes. Exit codes are already correct (2).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#247