-
Notifications
You must be signed in to change notification settings - Fork 67
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
xmitgcm dev branch: possible bug/broken dependency #224
Comments
Uriel! ❤️ ❤️ ❤️ Lovely to hear from you after a long time! Our CI contains an environment which will hopefully reproduce this error. I have opened #225, which we can use to dig deeper. |
Hi Ryan! Indeed It's been too long! :) Hope things are going well. Great. I'll leave this open in the meantime. |
rabernat
added a commit
to rabernat/xmitgcm
that referenced
this issue
Nov 12, 2020
rabernat
added a commit
to rabernat/xmitgcm
that referenced
this issue
Nov 12, 2020
fraserwg
pushed a commit
to fraserwg/xmitgcm
that referenced
this issue
Nov 23, 2021
* empty commit to trigger CI * add test for k_levels=[1] * add explicit test for MITgcm#233 * test for bug in llc90 * fixes MITgcm#224 * resolve final bugs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First off, thank you devs for this extremely useful library.
I have 0.4.1 running fine on my main workstation. I came across this issue while trying to install xmitgcm dev branch from scratch on a new machine. If a run this simple code:
I get this error:
I should emphasize that the code runs fine on xmitgcm 0.4.1 with fsspec 0.4.1, dask 2.4.0 and xarray 0.15.1. The error you see above is when trying to run current dev branch with fsspec 0.8.3, dask 2.27.0 and xarray 0.16.1.
I can provide pipenv lock files of both virtual environments to facilitate reproduction of the issue if that helps.
The text was updated successfully, but these errors were encountered: