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
fix: honor storage_options in save and save_group (#4415)
* fix: honor storage_options in save and save_group
`save` did not declare `storage_options`, so it landed in `**kwargs` and was
counted as one of the arrays to save. Passing it turned a single array into a
group holding `arr_0`, and the options never reached the store.
`save_group` resolved the store itself and then passed `storage_options` on to
`save_array` for positional arrays, where `make_store_path` rejects them as
unused. The keyword branch right below it already did the right thing.
* test: skip the fsspec URL case on the min-deps job
An fsspec URL for a sync filesystem is opened through AsyncFileSystemWrapper,
which landed in fsspec 2024.12.0, and the min-deps CI job pins an older one.
Same guard the fsspec store tests already use.
* docs: rename changelog fragment to the PR number
Assisted-by: ClaudeCode:claude-opus-5-5
---------
Co-authored-by: Davis Vann Bennett <davis.v.bennett@gmail.com>
`zarr.save` now takes `storage_options` as an option instead of treating it as one of the arrays to save: saving a single array with `storage_options` set no longer produces a group holding `arr_0`, and the options now reach the store. `zarr.save_group` no longer fails with `'storage_options' was provided but unused` when the arrays are passed positionally.
0 commit comments