Lachlan Deakin

> Is there interest in integrating a `FilesystemStore` with direct I/O capabilities into `zarrs` Yes! This looks great and I would probably use it myself. Thanks for putting together such...

Thanks for your work on this @sk1p! xref direct IO PRs and comments related to compressed writing/potential further improvements: - #58 - [requesting a buffer from storage](https://github.com/LDeakin/zarrs/pull/58#issuecomment-2315773339) - [partial encoder-like...

Related idea https://github.com/zarr-developers/zarr-specs/issues/346

> @LDeakin I saw that you at least started on this at [LDeakin/zarrs#55](https://github.com/LDeakin/zarrs/pull/55). Anything come up in your implementation that might adjust what you want to see in the spec?...

@joshmoore > Your use of `"must_understand"` does the minimum required by the text of the spec, but what it doesn't do is allow us to change anything about this proposal...

Now that ZEP0009 exists (and looks pretty good IMO), it would make sense for `consolidated_metadata` to look like this: ```json { "zarr_format": 3, "node_type": "group", "extensions": [ { "name": "consolidated_metadata",...

I have been using sparse images with `vulkano` where I manually manage allocations and binding. I had to make [a few small changes](https://github.com/vulkano-rs/vulkano/compare/master...LDeakin:vulkano:sparse_images) to `vulkano` though: - Uncomment `ImageCreateFlags::SPARSE_BINDING` etc...

I've added read support for HTTP stores in `zarrs_tools` version 0.5.5 with #11. ```bash zarrs_reencode https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0001A/2551.zarr/C/3/0/0 2551.zarr/C/3/0/0 ``` Writing to remote stores is not supported, and I am not sure...

> A consequence of this design is that every new data type requires creating a new array-bytes codec, Hopefully not. We are already defining how extension data types interact with...

> (I think we could salvage this PR by changing some "MUST support" statements to "SHOULD support") This is in line with my thoughts in #293: > A zarr implementation...