zarr-developers / jzarr Goto Github PK

• blosc results differ (see below)
• why did only the maven build fail??

https://github.com/zarr-developers/jzarr/actions/runs/5335179085/jobs/9668035098#step:5:1412

Warning:  Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.011 s - in com.bc.zarr.BloscCompressorTest
[INFO] 
[INFO] Results:
[INFO] 
Error:  Failures: 
Error:    ZarrArrayTest_saveMultithreading.parallelWriting_toTheSameChunk_withCompression_blosc:101->multithreaded_write_read_roundtrip:154 
Expected: is <0>
     but: was <19>
Error:    ZarrArrayTest_saveMultithreading.parallelWriting_toTheSameChunk_withCompression_blosc_With_ZipStore:83->multithreaded_write_read_roundtrip:154 
Expected: is <0>
     but: was <19>
[INFO] 
Error:  Tests run: 156, Failures: 2, Errors: 0, Skipped: 1

cc: @melissalinkert @pedson @MSanKeys963

Currently the pages at https://jzarr.readthedocs.io/ are built from https://github.com/bcdev/jzarr.

I recently reached out to the good folks at https://github.com/bcdev about clarifying this situation.

While this works very elegantly in the context of artifact publication via GitHub Actions, this breaks local developer workflow while running mvn install. Supporting both workflows might require defining a profile to allow the artifact signing to be triggered conditionally.

Hi,

When creating Blosc compressor with

Compressor compressor = CompressorFactory.create("blosc", "cname", "zstd", "clevel", 9, "blocksize", 0, "shuffle", 1);

A new optional parameter for Blosc "nthreads" is added into the .zarray metadata file as

"numThreads" : 1

And this is what I got when reading this Zarr with the Python API

  File "numcodecs\blosc.pyx", line 548, in numcodecs.blosc.Blosc.__init__
TypeError: __init__() got an unexpected keyword argument 'numThreads'

Since 'numThreads' is in metadata files it's not possible anymore to read the resulting Zarr using Python
It's technically a Python error, but since JZarr data has to be compatible with the Python API I think it's more of a Java issue (or did I just do something wrong ?)

• bump version (dropping SNAPSHOT)
• create a release & a tag in GH web UI
• wait for GH action to pass
• go to https://s01.oss.sonatype.org/#stagingRepositories
• "close" the repository
• wait for the sonatype build to pass
• "release" the repository
• wait for maven central to update (https://central.sonatype.com/artifact/dev.zarr/jzarr/0.3.7/versions)
• profit