-
Notifications
You must be signed in to change notification settings - Fork 51
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
Revert to pre-2023.3.15 tifffile to avoid mm_stack issue #529
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #529 +/- ##
=======================================
Coverage 93.98% 93.98%
=======================================
Files 53 53
Lines 4658 4658
=======================================
Hits 4378 4378
Misses 280 280
☔ 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.
I am totally fine with this considering we are moving to plugin bioio stuff.
Whenever this is released it honestly might warrant a breaking change bump.
"xarray>=0.16.1,<2023.02.0", | ||
"xmlschema", # no pin because it's pulled in from OME types | ||
"zarr>=2.6,<3", | ||
"zarr>=2.6,<2.16.0", |
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.
just curious, do you happen to know why we have to do the zarr constraint?
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.
The _get_image_data()
relies on reading the image data as zarr per the argument aszarr
Description
Attempt to resolve issue installing
aicsimageio
with conflictingbfio
dependencies due to changes in >2023.3.15 tifffile
. This largely just reverts this PRTesting
Unit tests