-
Notifications
You must be signed in to change notification settings - Fork 18
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
Error using client.listdir() on a canfar directory with 100s of files. #228
Comments
Hmm. Not sure what is going on. Is it reproducible? Sometimes these errors could be caused by intermittent networking/storage issues. I've tried to run it but I don't have access to it. Also, are you able to list other directories in the path? |
Can confirm that the error is reproducible, since it's still throwing the same error for me. Indeed every time on the same file. Other directories in the path work fine. Both higher directories and a subdirectory I just created with only 1 file. However, I think it is related to the number of files, because when I executed the following small test:
and then try to listdir that directory in CANFAR, it breaks consistently on file
|
Steps to reproduce:
Throws error |
Thanks for the details - I'm now able to reproduce it. We are working on a patch, but until then if you need to list the content of that directory please use the |
Thanks, the I know the |
@ErikOsinga - the latest release ( |
I'm running into a vague error using the commands
which returns
OSError: [Errno 400] OptionNotSupported: batch container node listing: limit ignored, resume not implemented
I'm pretty sure it's not a certificate or permission error, since I've previously been able to run this command when the directory was less populated, and I'm able to
listdir()
the directory(ies) above it without problems.This makes me think it's likely some kind of processing limit, perhaps because of the amount of files in the folder? Though not overly large, the folder I'd like to listdir contains 572 files.
Full code error:
The text was updated successfully, but these errors were encountered: