If not, it means there was a data corruption / bug somewhere in the ingestion process or database, and it means to be fixed.
Incorrect hashes would also prevent replay on storage instances with the validating storage proxy enabled.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T3135 Improve integrity of ingested content | ||
| Migrated | gitlab-migration | T399 (Re-)Compute data checksums before insertion | ||
| Migrated | gitlab-migration | T3010 Enable the validating storage proxy in production | ||
| Migrated | gitlab-migration | T3012 Check all objects in the production storage/journal have a correct hash |
Event Timeline
Comment Actions
This is a duplicate of T75, the history of which would probably be useful to take into account (I suspect it can be closed).
There's also a few known bugs in imported data, e.g. zero-padded directories https://github.com/pallets/flask/issues/2029.