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
If you then try unzip -l a.zip, you will see the length of foo listed as 4 bytes, as opposed to the correct length of 16 bytes, which you can verify by doing the above with a DirectoryStore. This results in the zipfile being corrupted. I have submitted a pull request for the one-liner fix here:
orenwatson
changed the title
Zipfile produced by Zip store has incorrect length stored
Zipfile produced by Zip store has incorrect length stored (and hence wrong cksum)
Jan 5, 2022
You can reproduce this by doing this in the python REPL:
If you then try
unzip -l a.zip
, you will see the length of foo listed as 4 bytes, as opposed to the correct length of 16 bytes, which you can verify by doing the above with a DirectoryStore. This results in the zipfile being corrupted. I have submitted a pull request for the one-liner fix here:#930
This bug is present in zarr version 2.10.3 up to the current master branch.
The text was updated successfully, but these errors were encountered: