Skip to content

The guard's case-insensitive lane lookup (rows_named_ci_alias) and session-start's (lane_named_ci) still read an unreadable register as no row (follow-up to #310) #315

Open

Description

@brettheap

The follow-up named in #310's design (R5, #310 6350725057) and in lane 3's review of it (#310 6351763793: R5 and NIT 587). It is filed on Brett Heap's approval, given in lane 3's session at about 21:44Z on 2026-10-22.

#310 makes canon_lane refuse every name over an unreadable register (Brett's R1, "Refuse", #310 6351997987). The two case-insensitive lookups below are outside that change.

What is wrong

Direction

Not started: v1.2.0 work waits for the v1.1.0 tag and Brett's word.

Activity

  1. added this to the v1.2.0 milestone on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions