Skip to content

fix: fractal_fsspec_store probes zarr.json so OME-Zarr 0.5 stores open - #290

Merged
lorenzocerrone merged 1 commit into
mainfrom
fix/fractal-fsspec-store-zarr-v3
Nov 16, 2026
Merged

lorenzocerrone merged 1 commit into
mainfrom
fix/fractal-fsspec-store-zarr-v3

Conversation

@lorenzocerrone

Copy link
Copy Markdown
Collaborator

Closes #289.

fractal_fsspec_store checked the URL by fetching only the zarr v2 keys (.zgroup, .zarray), so every OME-Zarr 0.5 / zarr v3 store raised NgioValueError("Store ... can not be read") even when the data was reachable. The probe now tries zarr.json first.

  • Regression test: a local store served over HTTP, opened through the helper, parametrised over 0.4 and 0.5 (the 0.5 case fails without the fix).
  • Extra test: a URL with no zarr behind it still raises.
  • Changelog entry under [Unreleased].

Not covered: the 401 token errors on a v3 store (no token-protected server in the tests). The handling in _probe_key does not depend on the key.

🤖 Generated with Claude Code

#289)

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@codecov

codecov Bot commented Nov 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@lorenzocerrone
lorenzocerrone merged commit 7f576cb into main Nov 16, 2026
13 checks passed
@lorenzocerrone
lorenzocerrone deleted the fix/fractal-fsspec-store-zarr-v3 branch November 16, 2026 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fractal_fsspec_store rejects OME-Zarr v0.5 (zarr v3) stores: probe only checks .zgroup / .zarray

1 participant