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

Revert to pre-2023.3.15 tifffile to avoid mm_stack issue #529

Merged
merged 2 commits into from
Sep 26, 2023

Conversation

SeanLeRoy
Copy link
Collaborator

Description

Attempt to resolve issue installing aicsimageio with conflicting bfio dependencies due to changes in > 2023.3.15 tifffile. This largely just reverts this PR

Testing

Unit tests

@codecov-commenter
Copy link

codecov-commenter commented Aug 16, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (04a92f7) 93.98% compared to head (e086c86) 93.98%.

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           
Files Changed Coverage Δ
aicsimageio/readers/ome_tiff_reader.py 95.08% <100.00%> (ø)
aicsimageio/readers/tiff_glob_reader.py 86.77% <100.00%> (ø)
aicsimageio/readers/tiff_reader.py 95.21% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@evamaxfield evamaxfield left a 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",
Copy link
Collaborator

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?

Copy link
Collaborator Author

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

@SeanLeRoy SeanLeRoy merged commit 1e3d0ad into main Sep 26, 2023
140 of 148 checks passed
@SeanLeRoy SeanLeRoy deleted the feature/adjust-tifffile-versioning branch September 26, 2023 15:26
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants