Skip to content

Files corrupted after connection reset during CLI upload #3424

@tsalo

Description

@tsalo

What went wrong?

I was uploading a fairly large dataset (~340 GB) with the CLI. At the 99.25% mark, the connection reset and the transfer stopped. The transfer failed at 1452/1463 files, and when I go on OpenNeuro, the dataset validation is failing because 10 NIfTIs have unreadable headers (likely corrupted).

I tried calling the upload command again in case it would pick up where it failed, but it just says that the dataset is up to date and doesn't push anything. I also tried locking and re-unlocking the problematic files (this is the same datalad dataset as in #3421), but that didn't register as a change to push for the CLI.

Expected behavior

I expected the CLI to continue the upload from where it failed in my first attempt.

How to reproduce

  1. Begin upload to OpenNeuro with CLI.
  2. Stop partway through? Maybe it has something to do with being so close to done (99.25%).
  3. Restart upload.

Desktop

  • OS: Linux
  • Browser: n/a
  • Version: n/a

Phone

  • Device: n/a
  • OS: n/a
  • Browser: n/a
  • Version: n/a

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions