-
Notifications
You must be signed in to change notification settings - Fork 33
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
core dump or ignored exceptions on shutdown when reading from s3fs using fsspec #80
Comments
When additionally I try to use fsspec blockcache I get additional tracebacks. Using
I get:
That may be related to fsspec/filesystem_spec#404 |
This sounds a lot like #50. The summary of that issue is that almost any use of |
@gerritholl I can't reproduce this with a fresh install. Could you please check again so that we might close this issue? |
This seems to be fixed in master now. At least, if |
When I try to read a file opened using
fsspec.open
, I get a fatal Python error (core dump) on shutdown.Using:
and then running with
python -X dev
gives:when wrapping the opening in a context manager, the core dump is apparently averted, but there are still ignored exceptions reported on shutdown. Using:
gives
It is puzzling that the traceback starts at the
print
line, despite the value being read out and printed to the console correctly.I'm using fsspec 0.8.3, h5netcdf 0.8.1, netcdf4 1.5.4, s3fs 0.5.1, on Python 3.8.5 on openSUSE 15.0.
The text was updated successfully, but these errors were encountered: