Unpin fsspec #508
Labels
Comments
tcompa
added a commit
that referenced
this issue
Sep 4, 2023
tcompa
added a commit
that referenced
this issue
Sep 4, 2023
Add constraint for fsspec version (ref #508)
This was referenced Sep 4, 2023
tcompa
added a commit
that referenced
this issue
Sep 25, 2023
1 task
tcompa
added a commit
that referenced
this issue
Sep 27, 2023
github-project-automation
bot
moved this from TODO
to Done
in Fractal Project Management
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Something fails when passing from fsspec 2023.6 to 2023.9, but a quick look at the release notes (https://filesystem-spec.readthedocs.io/en/latest/changelog.html) does not immediately suggest the reason. We depend on fsspec through dask, but I could not readily find any bug report over there.
The same issue was found for ome-zarr-py: ome/ome-zarr-py#302.
Let's now pin fsspec version to 2023.6, to fix the CI. This is a placeholder issue, for unpinning the dependency in the future (possibly with a
!=2023.9constraint), when the issue is identified and fixed - either upstream or in fractal-tasks-core.The text was updated successfully, but these errors were encountered: