Skip to content

Conversation

charles-turner-1
Copy link
Collaborator

@charles-turner-1 charles-turner-1 commented Aug 8, 2025

Change Summary

  • Update to zarr v3. Currently pinned to versions >= 3.1, going to see if we can relax this and allow v2 & v3.
  • Add 'asynchronous': True to test_open_dataset_kerchunk - fails otherwise. We probably want to add this to the documentation?

Related issue number

#727

Checklist

  • Unit tests for the changes exist
  • Tests pass on CI
  • Documentation reflects the changes where applicable

Copy link
Collaborator

@mgrover1 mgrover1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only comment here is to add this in the docs under the catalog spec section, other than that, this looks great! 🎉

https://intake-esm.readthedocs.io/en/stable/reference/esm-catalog-spec.html#

@charles-turner-1
Copy link
Collaborator Author

@mgrover1 not quite sure what you meant by that so I might have gone a bit overboard - added distinct zarr2 and zarr3 data formats too.

Some tests that I added in a recent PR apparently didn't get merged & got dragged in with this PR. I'll see if I can get codecov running again so I don't make any more mistakes like that...

@charles-turner-1
Copy link
Collaborator Author

@martindurant does intake have a codecov account? I'd like to get the code coverage CI step running again if possible.

Copy link
Collaborator

@mgrover1 mgrover1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for specifying zarr2 vs zarr3 here which will help with backwards compatibility 🎉

@martindurant
Copy link
Member

does intake have a codecov account

Sorry, no.

@charles-turner-1 charles-turner-1 merged commit b9c14d9 into main Aug 15, 2025
10 checks passed
@charles-turner-1 charles-turner-1 deleted the 727-allow-zarr-3 branch August 15, 2025 02:00
charles-turner-1 added a commit that referenced this pull request Aug 21, 2025
* Tests all passing? Deps must have updated since I last tried

* Missing environment bits

* Apparently the bugfix was in zarr v3.0.10

* Fix requirements in ci/env*.yml

* Allow zarr <3.0 or >=3.0.10

* Change async in test based on zarr version - we can make this default behaviour too I think

* Move `_zarr_async` to utils module

* Add asynchronous/synchronous note to docs under Assets object section. I think we can do better & take care of this for the user

* @mgrover1 comment, add some extra tests, allow zarr version specification in the data format

* Misformatted esm-catalog-spec

* Re-pin minimum zarr version

* Formatting
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.

3 participants