-
Notifications
You must be signed in to change notification settings - Fork 5
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
542 xarray #543
542 xarray #543
Conversation
…fore pushing the image 👠" This reverts commit a828dfd.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #543 +/- ##
==========================================
+ Coverage 64.75% 65.85% +1.09%
==========================================
Files 48 48
Lines 4687 4750 +63
==========================================
+ Hits 3035 3128 +93
+ Misses 1652 1622 -30 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 💯
@kenfus is it okay to remove |
An update, with pandas >=2, the following FutureWarning occured:
|
…r past releases 💉
I also removed the build-string fixations, because they prevent updates on dependency-constraints. Therefore, I introduces the following instructions to the README of the Feedstock & triggered the according builds there. Updating an already existing Wheel: It may happen that an update of a dependency (direct or transversal) introduces a breaking change in a future release. Then, the current constraints of an existing conda-wheel would be outdated an will most likely result in a broken environment. To prevent this, updating the according meta.yaml and increase the build-nr is not enough, because the solver doesn't just consider the largest build-numbers of conda-wheels. So, to fix this for current and also older releases, you have to relabel oudated conda-wheels to |
I rather not. This was requested by @rohitcbscient and it also works in the current example of the |
Okok. Not sure what failed though, because after everything has settled, it works for me as well. However, I still improved the function by not changing the imager-fields permanently just because of a guess-function. Update will soon be available. |
See issue #542
Additional bug fixing and minor improvements
Unfortunately, I created this branch from 512_sarus and not from main, if you wonder why there are so many commits.