Tom Augspurger

It should be automated through GitHub Actions on tags. > On Nov 14, 2024, at 8:28 AM, Martin Durant ***@***.***> wrote: > > > @TomAugspurger , you can dd me...

Fixed some merge conflicts and changed the `_convert_{to,from}_nvcomp_arrays` methods to be sync.

@d-v-b f16d730b9b5b13bcfec934cd26ccee0cd8a6e466 fixes an issue after https://github.com/zarr-developers/zarr-python/pull/3228 I think. Where providing an alternative zstd implementation here, so when we figure out which codec to use when creating an array, we...

Akshay responded on this point [in February](https://github.com/zarr-developers/zarr-python/pull/2863#issuecomment-2691011494)(!) @dstansby could you at least respond to that directly: that this is a *wrapper* around a codec engine, in exactly the same way...

> where is the source code for the nvcomp zstd implementation, and the python bindings? I don't believe that the source code for those are published publicly.

> If we cannot inspect the source code for this codec, and we cannot submit patches, then I would definitely not be interested in experiencing bugs from it. Is that...

> Sorry, I missed that. And sorry for the slow reply - I am not paid to work on zarr-python, and review stuff on a best efforts basis. Likewise :/...

> I think there should be tests that compare the compression/decompression https://github.com/zarr-developers/zarr-python/pull/2863/files#diff-b4b3e1bcdd519d839ba90f79f062ef0147362dbac854af26f871b53796791f21R69 has that. I believe that all the comments have been addressed now but let me know if I...

> For this particular feature, what would it look like if we spun it off into a separate repo under the zarr-developers org? Let's see: For users, I think it...

We talked about this a bit at last week's dev call. I think there's general agreement that native support for GPUs is important. And that at a technical level developing...