Closed yarikoptic closed 2 years ago
yeap, it's consistent/reproducible.
When you moved the files in .dandi
in Zarr 7723d02f-1f71-4553-a7b0-47bda1ae8b42 from git-annex to git, you did it wrong, and now the contents of, say, .dandi/s3sync.json
are literally "/annex/objects/MD5E-s143--b49b3643ca01ab4b71558fe234aa98df.json
".
@yarikoptic I've deleted the .dandi/s3sync.json
and .dandi/zarr-checksum
from the Zarr backup in question. The next run of the script should recreate them.
oh... commits in question are e.g. https://github.com/dandizarrs/7723d02f-1f71-4553-a7b0-47bda1ae8b42/commit/2f8205262c9387552268411827ebd13ad5bf577f where indeed I just made it from a regular annexed file into unlocked annex file. Let's hope that rerun would address that. Doing it now! Thanks!
I think it is all ok now
With #235 merged (not sure if related though since backtrace seems about zarr) run of main script (not populate*) failed for one dandiset with
I will rerun now with #236 merged to see if reproducible.