Tom Nicholas

> think the (only?) solution I guess in this case even variable-length chunks wouldn't save us because this would actually require "ragged" chunks (i.e. no longer a rectilinear array of...

Okay now it did trigger? I'm confused what happened there.

I wouldn't say this issue is fully closed yet. See https://github.com/zarr-developers/VirtualiZarr/issues/281#issuecomment-2445526098 for an explanation. #191 closes an important part of it but #224 is also required.

We need some test cases to start explicitly checking behaviour for these cases. Unfortunately kerchunk doesn't seem to have any (see https://github.com/fsspec/kerchunk/issues/436). This is a little worrying because this seems...

> have a check on the constructor to forbid creating an array that actually has any chunk other than the last be of different length. A better place to have...

Thanks for raising this @rsignell , and for tracking this down @keewis and @sharkinsspatial! > v3 arrays have a chunks property to maintain https://github.com/zarr-developers/zarr-python/pull/1929 but for clarity we likely want...

I would expect that error (which could be clearer) to only be raised if you attempt to concatenate two variables with different dtypes. Are you sure that the `time_bnds` and...

I think this is all expected behaviour (if hidden behind many unintuitive defaults). The only bit that doesn't make sense to me is the idea that concatenating variables of the...

@ayushnag is there a way to identify a DMR++ file automatically? e.g. a [file magic](https://en.wikipedia.org/wiki/List_of_file_signatures)?

I'm not sure why this operation requires indexing at all... Can you open the files individually and then concatenate them to try to narrow down where / for which dataset...