Skip to content

Initial Manifest Path not Found #60

@amhanson9

Description

@amhanson9

One theme for validation errors is that the path wasn’t found when the initial manifest was created, meaning there is no MD5, and it is guaranteed to fail. Can this script be updated to get fixity information in another way? There were a high proportion of weird characters, but not always, and I was able to find these with os.walk(). For examples, look at manifests with errors from the first hub monitoring in 2025.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions