-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support fsspec 2023.10.0 #6333
Comments
- the nl server uses the package `datasets` which uses the package `fsspec`. The most recent version of `fsspec` causes problems with `datasets` as mentioned here: huggingface/datasets#6333
- the nl server uses the package `datasets` which uses the package `fsspec`. The most recent version of `fsspec` causes problems with `datasets` as mentioned here: huggingface/datasets#6333
- the nl server uses the package `datasets` which uses the package `fsspec`. The most recent version of `fsspec` causes problems with `datasets` as mentioned here: huggingface/datasets#6333
Hi @tomscholz, Thanks for pointing this out. I think you are right. I am doing some cross-checks and fixing it. |
Hi again, @tomscholz. After a more cautious investigation, I think the pin is OK because there are other reasons for it. Chronologically:
The reason is that after version 2023.10.0, they changed again the behavior of their Note:
|
Once root issue is fixed, remove temporary pin of fsspec < 2023.10.0 introduced by:
Related to issue:
As @ZachNagengast suggested, the issue might be related to:
The text was updated successfully, but these errors were encountered: