Skip to content

verify render: NONE line may read as clean when select's unknown_because is set #113

Closed

Description

@inth3shadows

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.

Activity

  1. inth3shadows commented on Oct 30, 2026

    @inth3shadows
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions