-
Notifications
You must be signed in to change notification settings - Fork 364
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
I/O operation on closed file #1032
Comments
Yes, there is a known regression that I should be able to clean up this morning. |
Is it possible to yank the bad version? Our builds also failed to this (we are now pinning it back) |
The fixed version is now out. Do you still need the yank> |
Hi! I'm still having this issue on version 2022.8.1. I get this error when I use |
Hi, I get the same error when writing to S3 with |
We didn't need the yank since we back pinned, however this thread seems to have continued |
Sorry for the mess. I yanked and made 2022.8.2 which should work for everyone. |
Thanks for your quick resolution. This package has huge indirect exposure since pandas depends on it, so errors propagate quickly :) |
...which is both good and bad. Created #1036 to try to do a better job at this. |
IMO a very simple test is simply
we use this extensively - fsspec is mentioned even in the pandas documentation for |
The latest version has broken our CI, but it might be that you've just exposed an issue in
dask
and I actually need to create a ticket there instead. This test worked fine atfsspec==2022.7.1
.Callstack
Repro case
The text was updated successfully, but these errors were encountered: