-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assertion error on digest type #1553
Comments
happened agin
need to do type checking etc. |
we encounter zarr for which we have size and checksum 0
although files are uploaded
and that zarr is still pending! ❯ curl --silent -X 'GET' 'https://api.dandiarchive.org/api/zarr/7933bc72-ec3f-4043-8076-d7aa8a70e4f7/' -H 'accept: application/json' -H 'X-CSRFTOKEN: wTUZx1u5sMThqoLPhpAxD6TubffnRiFNTWXBxjXPRokYFa3kNB71LWKnwuJndJcA' | jq .
{
"name": "sub-I48/ses-SPIM/micr/sub-I48_ses-SPIM_sample-BrocaAreaS03_stain-Somatostatin_SPIM.ome.zarr",
"dandiset": "000026",
"zarr_id": "7933bc72-ec3f-4043-8076-d7aa8a70e4f7",
"status": "Pending",
"checksum": null,
"file_count": 0,
"size": 0
} so we are back in the effects of various issues with zarrs in the dandi-archive: |
ok, so in this case we have downloaded some incomplete version of zarr, its checksum is null etc. We should at least issue a warning of some kind that upload was never finalized and they fetched potentially an incomplete copy . The zarr in question has already 27G in size odd, interrupted and restarted with refresh completed without error
so we might not be checking upon refresh??? |
repeated afresh, indeed -- no error if refresh after failed process
|
while trying to figure out
on drogon, got in
and of cause we do not know what type it is ...
The text was updated successfully, but these errors were encountered: