-
Notifications
You must be signed in to change notification settings - Fork 25
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
test_roundtrip
failing builds
#237
Comments
Digging deeper. pydata/xarray#8201 landed in Xarray v2023.09.0 which then caused a new bug that looks similar pydata/xarray#8271 which should be fixed by pydata/xarray#8272 If I anti-pin Xarray to resolve to another version ( |
If I test locally against upstream ( For now I'm going to anti-pin Xarray in requirements. |
v2023.09.0 of Xarray caused our Zarr roundtrip tests to fail as times no longer matched. For full details see xpublish-community#237 The fix looks to have landed in pydata/xarray#8272 and tests against the latest commit works, so we'll go with setting an pin to skip just v2023.09.0. Closes xpublish-community#237
* Anti-pin the latest version of Xarray to v2023.09.0 of Xarray caused our Zarr roundtrip tests to fail as times no longer matched. For full details see #237 The fix looks to have landed in pydata/xarray#8272 and tests against the latest commit works, so we'll go with setting an pin to skip just v2023.09.0. Closes #237 * Dev requirements needs to mirror requirements due to --no-deps
xpublish/tests/test_zarr_compat.py
Lines 140 to 156 in c4134db
Is causing builds with unrelated changes to fail recently.
It looks like the issue is due to the time encoding.
A warning is getting thrown earlier
Which is from here:
xpublish/xpublish/utils/zarr.py
Lines 132 to 155 in c4134db
But is really coming from the Xarray Zarr backend.
https://github.com/pydata/xarray/blob/25e6e084aa18c49d92934db298a3efff9c712766/xarray/backends/zarr.py#L288-L318
The text was updated successfully, but these errors were encountered: