Josh Moore

Still green after an update to `2.11.1`. Probably the biggest question from my side is what _else_ should fall into the `set_option` category to know if the design is right.

The more I come back to this, @willirath, the more I feel that _either_ values like `write_empty_chunks` should _also_ be part of `set_options` _or_ `fill_missing_chunks` should be an `__init__` argument...

@ptallada: interesting! I would have thought that would work as well. I assume the issue you are dealing with is that the first array was created without a `store` instance....

I'd propose that this could likely be migrated to zarr-specs if not a more design-y or perhaps community repo. cc: @ivirshup in case there's interest.

Hi @vladpopovici. It's a good point. @abergou also pointed it out in https://github.com/zarr-developers/zarr-python/issues/552. Still open to solutions.

Not that I know of, sorry.

Hi @parthxtripathi. > can i work on this? That'd be great. Sure. > Could you please let me know what all pre-commit checks are required in zarr? I imagine we...

> I can recommend adding a minimal `pre-commit` configuration in a PR, then adding additional rules one-by-one in separate PRs Thanks, @benjeffery. @parthxtripathi, following that logic, I could see this...

A huge thanks to everyone for the contributions to the thread so far! There's likely enough content here that we may need to extract some of it into a dedicated...

The short version is that previously all (meta)data needed to open a group was at one location but now there is root metadata and the metadata tree is separated from...