Skip to content

Windows receipt inspection uses an ordinary filename for long workbench paths #2378

Description

@mldangelo-oai

Observation

The Python finding-issues inspection path calls stat() on the ordinary workbench filename and uses that spelling to construct a read-only SQLite URI. A Windows process subject to the legacy path limit can therefore fail to inspect an existing receipt store whose directory fits the limit but whose database filename crosses it.

Local evidence

With synthetic local scan data and a 244-character state directory, the resulting database filename was 262 characters. A test double that rejects only the ordinary long filename observed the same read-only URI in two checkouts of the same publication code. Inspection used local data. The test machine has OS long-path support enabled, so the legacy-policy failure was simulated.

Suggested coverage

Exercise local receipt inspection against an existing store under a legacy-policy path boundary. Preserve read-only mode, escaping, the existing missing-store behavior and support for UNC filenames.

Activity

  1. added
    bugSomething isn't working
    platform:windowsWindows, PowerShell, Windows paths, or Windows ACLs
    area:artifactsSaved scan state, storage, sealing, recovery, history, and artifact integrity.
    on Nov 15, 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

    area:artifactsSaved scan state, storage, sealing, recovery, history, and artifact integrity.bugSomething isn't workingplatform:windowsWindows, PowerShell, Windows paths, or Windows ACLs

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions