You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
verify render: NONE line may read as clean when select's unknown_because is set #113
Severity: Low · Status: needs verification (one verifier observed it; the code calls sel.none_is_unknown, so it may be a rendering-order issue rather than a missing signal)
Where:testgraph/verify.py:277-281
Claim: with no journeys selected and several warnings, verify printed journeys selected: NONE — nothing to verify as its headline. The UNKNOWN reasons only appear as indented lines below it. select and hook instead put "UNKNOWN, not verified-safe" in the headline itself (issue #75's rule).
Suggested fix: use the same two-sentence headline as select._render when unknown_because is non-empty.
Fixed in #141 (437c5e6): verify's NONE headline now reads journeys selected: NONE — but UNKNOWN, not verified-safe: when unknown_because is set, and that run exits 3 instead of 0.
Activity
fix: an unmodeled diff path degrades to every journey; verify's UNKNO…
inth3shadows commentedon Oct 30, 2026
Fixed in #141 (437c5e6): verify's NONE headline now reads
journeys selected: NONE — but UNKNOWN, not verified-safe:when unknown_because is set, and that run exits 3 instead of 0.