Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[titiler.xarray] update for Zarr 3.0 #1068

Open
vincentsarago opened this issue Jan 9, 2025 · 1 comment
Open

[titiler.xarray] update for Zarr 3.0 #1068

vincentsarago opened this issue Jan 9, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@vincentsarago
Copy link
Member

https://zarr.dev/blog/zarr-python-3-release/

we also need to pin zarr to 2.0 https://github.com/developmentseed/titiler/actions/runs/12695652933/job/35388000642?pr=1067

@vincentsarago vincentsarago added the bug Something isn't working label Jan 9, 2025
@maxrjones
Copy link
Member

The failing tests seem to fall into two categories.

  1. TypeError: Unsupported type for store_like: 'FSMap'.

This is being tracked by pydata/xarray#9957 and zarr-developers/zarr-python#2706. I expect this functionality will get implemented upsteam (and can see if it's something I could help with), so the solution here is likely to keep the pin on Zarr Python < 3.0 until that feature is implemented and released.

  1. TypeError: Object 0 has an invalid type for "path": int

It seems that int keys were likely automatically cast to strings in zarr python 2.0 but are not in zarr python 3.0. I think we could fix this easily on our end by parameterizing string keys rather than ints in

Even in the Zarr V2 spec, keys needed to be ASCII strings so this seems mostly a user error to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants