-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
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
Labels
No labels