Joe Hamman

Hi @Ozaq -- sorry the documentation was not clear here and that you hit some issues with 3.1. A few comments and questions: 1. What broke with the 3.1 upgrade?...

> We need zarr-python>=3, which doesn't work with @jhamman's fork because it doesn't have tags for versions above 3.0.0b2 I just pushed tags to my fork!

@bakamotokatas - the blosc codec in numcodecs has an id of `blosc`, not `blosc2`. Can you share your array metadata (`.zarray`)? Do you know how this dataset was created? Is...

closing as stale, feel free to reopen if you are still running into this issue.

I'll throw an idea into the mix. We probably want two things: - `Store.get_size(key: str) -> int` - `Store.get_size_dir(path: str) -> int` Of course, `list_dir` + `get_size` would be the...

Okay, so the `Dataset` constructor needs to create a copy of the metadata. Could we include a argument to the constructor that copies the `.values` too? Obviously there is a...

I wonder if we can close this now that we've demonstrated some substantial improvements here: - Blog post: https://earthmover.io/blog/xarray-open-zarr-improvements - https://github.com/zarr-developers/zarr-python/pull/2519 - https://github.com/pydata/xarray/pull/9861

@DahnJ - I think this is a great step forward. I want @d-v-b to review this but from my perspective, it could go in now, even with the outstanding store...

@zarr-developers/python-core-devs - do we have any Window's ~aficionados~ capable developers here? We need to do a bit of work to tweak path handling in the `LocalStore` and it would be...

> fsspec has a decent amount of work for this which you can reuse. Can you provide some pointers? > Actually, could RemoteStore write to local too to avoid the...