-
-
Notifications
You must be signed in to change notification settings - Fork 329
upstream fsspecstore failures #2853
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
Comments
I think fsspecStore should explicitly pass asynchronous=True when using AsyncFileSystemWrapper. I note that this isn't actually a failure but a warning, but still. The trouble is, that the intent is to call the filesystems in async contexts (coroutine), but creating the FS is happening in blocking code. To get this specific test to pass, you could simply mark it async, but I think it's best to be explicit. (previously, AsyncFileSystemWrapper was always asynchronous, but it ought to be callable from blocking code too, not least by kerchunk) |
can you explain what this test actually does? from what I can tell |
Is is used in the isinstance, no? The point is, that although a file: URL is passed, you get an async wrapped instance back, not LocalFileSystem. |
aha somehow my eyes slid over the isinstance. in any case, this failure is blocking all PRs now so fixing this is very high priority |
regardless of the resolution of this particular test failure, I'm pretty sure PRs should not be blocked because of changes in our upstream dependencies |
in the interest of speed I committed the suggested fix to an open PR: eb6b2d8 |
closed via #2851 |
Getting failures in tests/test_store/test_fsspec.py::test_wrap_sync_filesystem, not sure what the underlying issue. The relevant test is here:
zarr-python/tests/test_store/test_fsspec.py
Lines 247 to 254 in 96c9677
Does anyone know why this might fail for python 3.13?this is probably due to unreleased changes in fsspec@martindurant any ideas for how we should change this test?
The text was updated successfully, but these errors were encountered: