-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix error in yokogawa-to-zarr (due to Pillow v10.1.0) #570
Comments
Current versions in fractal-tasks-core: |
I checked in https://github.com/fractal-analytics-platform/fractal-tasks-core/actions/runs/6531523635/job/17732909815?pr=571, and the latest Pillow version (10.1) is indeed responsible for this issue. I opened an issue at imageio: imageio/imageio#1044. Depending on how it works over there, we may want to temporarily constrain the Pillow version to <10.1. I suspect a similar issue may appear in scikit-image (see https://github.com/search?q=repo%3Ascikit-image%2Fscikit-image+%22.mode+%3D%22&type=code), but I'm not able to say whether we rely on these features. |
I checked (through a fractal-containers run of examples 01 and 02 from fractal-demos, using the I'm merging #571 for now, and will open a new issue as a reminder for relaxing this constraint as soon as there are relevant updates in imageio or pillow. |
…-in-yokogawa-to-zarr-due-to-pillow-version Test pillow 10.1 (ref #570)
Running fractal-demos example 01 via a fresh version of fractal-containers leads to a failed job, with the traceback below.
The obvious candidate explanation is https://pillow.readthedocs.io/en/stable/releasenotes/10.1.0.html#setting-image-mode:
The text was updated successfully, but these errors were encountered: