Tom Nicholas

Huh. I'm not sure I fully understand yet - is this an example of trying to auto-generate indexes? Or an xarray "virtual variable" thing (not virtual variable in the virtualizarr...

This is great, but ideally as many of these as possible would be fixed or documented upstream surely?

@dhruvbalwada does this fix the problem you reported in #504?

Thanks for raising this @frazane ! We clearly need to pass this information in. Just to clarify - it looks like the part of the VirtualiZarr code you're referring to...

When I try to run that example I get this error: ```python File "/Users/tom/.cache/uv/environments-v2/virtualize-kenda-kerchunk-fffb73731867bdee/lib/python3.12/site-packages/zarr/codecs/_v2.py", line 51, in _decode_single chunk = chunk.view(chunk_spec.dtype.to_native_dtype()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ValueError: When changing to a larger dtype, its...

FYI @frazane I would like to fix this but I'm going to release VZ now without this fix just because there are multiple other important fixes to get out there.

@ghidalgo3 that's exactly right. The only thing you've missed is that although writing out a "virtual" zarr store is a future aim, writing out actual kerchunk reference files works today!...

(@ghidalgo3 I replied in #171 so as to preserve the original topic of this issue)

Thanks for the report and investigation @rsignell ! I'll revert that PR now, and notify @d-v-b and @maxrjones because I don't really understand what happened there.

@maxrjones I think we need to think about what happens when we serialize a `memory://` virtual chunk to icechunk/kerchunk. Currently IIUC such a chunk stays as a `ManifestArray` upon creation...