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
What happened: part of the epic #967 (nemarOrg/nemar-cli) OpenNeuro 0-byte-content recovery. This dataset did not reach a complete state. The hardened finalize gate correctly did NOT publish incomplete data — the dataset retains its real (partial) state; nothing empty was published.
Triage action: A single file 403 upstream (1/65063). UNRECOVERABLE; leaving published-but-incomplete is reasonable given 1 object.
Refs: epic nemarOrg/nemar-cli#967; recovery run followed .context/recover-runbook.md. data_complete=0 is the honest catalog state until resolved.
Re-measured: above the 90% threshold, stays listed (#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):
on004624: 1 of 65063 data keys have no object. 99.998% of its data is available.
Above the 90% a listed dataset must reach, so ADR 0005 governs unchanged: the
dataset is listed, serves what it has, omits what it does not, and advertises
nothing it cannot deliver. No withdrawal, and the remaining gap is reported
rather than hidden.
One key of 65,063, and it is still advertised at nemar-s3 with no object behind
it -- a false presence claim of the #967 shape, which tells every clone to fetch
a byte range NEMAR does not hold. Not part of the 230 keys retracted across the
five anatomical datasets. Retract with nemar admin fleet key-registration on004624 --retract-false-claims --apply,
unless the single key is still recoverable, in which case fetching it is the
honest repair because it makes the claim true.
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.
2026-10-15 content-recovery probe: the sole missing annex key declares 6,488,064 bytes, while its pinned upstream object reports 6,520,832 bytes. The size mismatch fails validation, so no object was copied. Fresh registration read-back is 65,062 present/registered, 1 missing, and 0 false claims. The dataset remains incomplete; this issue stays open.
Activity
nemar-bot commentedon Sep 12, 2026
Relabelled (2026-09-12T03:02:07.468Z): cause changed: upstream-403 -> needs-triage.
No cause could be determined from the reported error. Open the workflow run to classify it by hand.
neuromechanist commentedon Sep 16, 2026
Re-measured: above the 90% threshold, stays listed (#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):on004624: 1 of 65063 data keys have no object. 99.998% of its data is available.Above the 90% a listed dataset must reach, so ADR 0005 governs unchanged: the
dataset is listed, serves what it has, omits what it does not, and advertises
nothing it cannot deliver. No withdrawal, and the remaining gap is reported
rather than hidden.
One key of 65,063, and it is still advertised at
nemar-s3with no object behindit -- a false presence claim of the #967 shape, which tells every clone to fetch
a byte range NEMAR does not hold. Not part of the 230 keys retracted across the
five anatomical datasets. Retract with
nemar admin fleet key-registration on004624 --retract-false-claims --apply,unless the single key is still recoverable, in which case fetching it is the
honest repair because it makes the claim true.
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 15, 2026
2026-10-15 content-recovery probe: the sole missing annex key declares 6,488,064 bytes, while its pinned upstream object reports 6,520,832 bytes. The size mismatch fails validation, so no object was copied. Fresh registration read-back is 65,062 present/registered, 1 missing, and 0 false claims. The dataset remains incomplete; this issue stays open.