You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-measured: below the 90% threshold (#1396, ADR 0064)
Re-measured against the bucket on 2026-09-16, on ADR 0064's basis (distinct
annexed keys, never tree entries and never total_files):
on008462: 443 of 563 data keys have no object. 21.3% of its data is available.
Below the 90% a listed dataset must reach. This dataset is not public, so there
is no live catalog entry advertising data it cannot serve; the gap is recorded
here rather than actioned as a withdrawal.
The first missing key is SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855,
which is the SHA-256 of the empty string: a zero-length file, legitimately empty
upstream. 120 further keys are in the bucket and unregistered, and are not
registered while content is missing (ADR 0061).
Verification basis: presence at declared size, so a zero-byte object left by
a failed copy counts as missing rather than present (#967). Size-level, not
checksum-level.
Progress update (2026-10-16 UTC): The subsequent recovery checkpoint records 443 objects (26,779,151,006 bytes) uploaded with per-object readback verification, followed by registration of all 563 current dataset-tree keys. This supersedes the September 16 measurement of 443/563 keys missing, which predates that work. The import job still reports copy / quarantined / unambiguous_orphan. The last recorded accounting is 563 tree/registered keys versus 564 bucket objects; the extra object remains unidentified. The manifest check previously found no version manifest, and there is still no supported read-only tree/manifest/object comparison. No finalization or publication was run in this recovery step. Next evidence needed is an approved list-only inventory or reviewed no-write comparison of the tree, manifest, and object keys/sizes. Please leave the issue open pending this reconciliation.
Activity
neuromechanist commentedon Sep 16, 2026
Re-measured: below the 90% threshold (#1396, ADR 0064)
Re-measured against the bucket on 2026-09-16, on ADR 0064's basis (distinct
annexed keys, never tree entries and never
total_files):on008462: 443 of 563 data keys have no object. 21.3% of its data is available.Below the 90% a listed dataset must reach. This dataset is not public, so there
is no live catalog entry advertising data it cannot serve; the gap is recorded
here rather than actioned as a withdrawal.
The first missing key is
SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855,which is the SHA-256 of the empty string: a zero-length file, legitimately empty
upstream. 120 further keys are in the bucket and unregistered, and are not
registered while content is missing (ADR 0061).
Verification basis: presence at declared size, so a zero-byte object left by
a failed copy counts as missing rather than present (#967). Size-level, not
checksum-level.
nemarAdmin commentedon Oct 16, 2026
Progress update (2026-10-16 UTC): The subsequent recovery checkpoint records 443 objects (26,779,151,006 bytes) uploaded with per-object readback verification, followed by registration of all 563 current dataset-tree keys. This supersedes the September 16 measurement of 443/563 keys missing, which predates that work. The import job still reports
copy / quarantined / unambiguous_orphan. The last recorded accounting is 563 tree/registered keys versus 564 bucket objects; the extra object remains unidentified. The manifest check previously found no version manifest, and there is still no supported read-only tree/manifest/object comparison. No finalization or publication was run in this recovery step. Next evidence needed is an approved list-only inventory or reviewed no-write comparison of the tree, manifest, and object keys/sizes. Please leave the issue open pending this reconciliation.