Josh Moore

> The codecov errors can be ignored. As far as I can see, all of them are false negatives. Or is the issue that the cupy tests aren't being run...

Hi @madsbk. No, sorry. This just landed on the vacation :mountain:. I'll start reviewing for a 2.13 release ASAP.

Rolling into a 2.13 pre-release. If anyone has any lingering concerns about the API, there would still be a (small) window to address them in.

zarr-python should work hard not to load the entire array, but will actively load the individual chunks. If you want to defer even that, you might want to look into...

Had looked at that one previously as well. :+1: All the better if your experiences have been good.

I'd hope it'd be easy enough to add an action that says, "must have fragment". Worst case: we can push it to the PRs manually. :wink:

Another possible option: https://sphinx-github-changelog.readthedocs.io/en/latest/ (...as I struggle with the anchors for pre-releases ...) cc: @MSanKeys963

- @jakirkham suggests https://github.com/regro/rever - @alimanfoo suggests looking at how dask does it. But generally, :+1: for: - keeping it simple - having a check on all PRs - ability...

Doh. Sorry, @maiia-pi, I somehow lost a comment I had prepared. More briefly, it looks like @d-v-b ran into this issue here: https://github.com/zarr-developers/zarr-python/pull/738/files#diff-f389c1f0162cd60b1b5a4187dad20dfd3d22c98da2ebe22e860ea830bc25a0e9R692 You might try to use his `zarr.util.all_equal`...

@DennisHeimbigner: `.zmetadata` is currently outside of the v2 spec (i.e. an implementation detail) like `dimension_separator` was.