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

CI failures: April 4 2023 #400

Closed
anissa111 opened this issue Apr 4, 2023 · 5 comments
Closed

CI failures: April 4 2023 #400

anissa111 opened this issue Apr 4, 2023 · 5 comments
Assignees
Labels
bug Something isn't working dependencies Pull requests that update a dependency file

Comments

@anissa111
Copy link
Member

anissa111 commented Apr 4, 2023

The release of pandas 2.0.0 seems to have broken a few things on our side

  • we should consider adding pandas to upstream testing
@anissa111 anissa111 added bug Something isn't working high priority dependencies Pull requests that update a dependency file labels Apr 4, 2023
@anissa111 anissa111 self-assigned this Apr 4, 2023
@anissa111
Copy link
Member Author

One of our dependencies seems to have pinned to the previous version of pandas, which is why our CI started passing again, I'm going to keep this issue open, as we should still update our package to work with pandas 2.0

@pilotchute
Copy link
Contributor

@cyschneck
Copy link
Contributor

cyschneck commented Oct 20, 2023

Currently, pandas is pinned to 1.5.3 as part of xarray<=2023.02.0 in environment.yml as a part of issue #381

xarray 2023.2.0 [required: >=0.18.0]
     ├─ numpy 1.23.5 [required: >=1.21]
     │  └─ dependencies of numpy displayed above
     ├─ packaging 23.1 [required: >=21.3]
     │  └─ dependencies of packaging displayed above
     ├─ pandas 1.5.3 [required: >=1.4,<2a0]
     │  └─ dependencies of pandas displayed above
     └─ python 3.11.5 [required: >=3.9]

@cyschneck
Copy link
Contributor

xarray unpinned as part of #381 (PR: #492) and Upstream-dev CI running against 381 branch completes without error

@cyschneck
Copy link
Contributor

Fixed and closed as part of PR #492. Expanded tests will part of #507 to catch future issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

4 participants