Skip to content

Import failure: on006110 (ds006110) #82

Open

Description

@neuromechanist

Dataset: on006110 | OpenNeuro source: ds006110
Missing objects: 10/66120 (at declared size, per nemar admin import verify)
Failure class: needs-triage

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: 10 objects missing after copy. Classify 403 vs shard gap; if shard, re-run recover.

Refs: epic nemarOrg/nemar-cli#967; recovery run followed .context/recover-runbook.md. data_complete=0 is the honest catalog state until resolved.

Activity

  1. added
    import-failureOpenNeuro import/recovery failed for a dataset
    needs-triageNo cause could be determined from the reported error; classify by hand from the run
    on Jul 22, 2026
  2. neuromechanist commented on Sep 16, 2026

    @neuromechanist
    MemberAuthor

    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):

    on006110: 3 of 59939 data keys have no object. 99.995% 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.

    Three keys of 59,939. 59,936 keys are present in the bucket and not recorded in
    the location log, which is the #1392 backlog; they are not registered while any
    content is missing (ADR 0061). This dataset is also where five .log.rmet
    retraction records (-) were first misread as part of the version id, which S3
    answers with a bare InvalidRequest.

    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.

  3. nemarAdmin commented on Oct 15, 2026

    @nemarAdmin
    Contributor

    2026-10-15 follow-up: the --include-incomplete registration apply recorded 59,936 of 59,939 bucket-present keys in the git-annex location log, verified all 59,936 entries, and pushed successfully (0 failures, 0 false claims). Three keys remain absent at their declared sizes and unclaimed. on006110 remains incomplete/quarantined, so this issue stays open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    import-failureOpenNeuro import/recovery failed for a datasetneeds-triageNo cause could be determined from the reported error; classify by hand from the run

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions