You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v2, we allow filters to be an empty array. But the v2 spec states that filters should be an array with at least one element, or None. So we should fix our implementation, and no longer generate metadata with an empty array of filters. For backwards compatibility, we should read the empty array of filters, and probably emit a warning.
The text was updated successfully, but these errors were encountered:
Linking the discussion for context. Can also show up when creating a format=3 zarr file, but I do not know if it might be intended for zarr format=3.
in the case of zarr v3, "filters" is a shorthand name for a type of codec that transforms arrays into arrays, and we do want to represent 0 of them as an empty tuple, so I don't think there's a problem there.
In v2, we allow
filters
to be an empty array. But the v2 spec states thatfilters
should be an array with at least one element, orNone
. So we should fix our implementation, and no longer generate metadata with an empty array of filters. For backwards compatibility, we should read the empty array of filters, and probably emit a warning.The text was updated successfully, but these errors were encountered: