You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
I can open an S3 file in root, but not in a subdirectory #62
Could you try to reproduce this using code from #60? (you can simply install fs-s3fs-ng package - it is the same as fs-s3fs==1.1.1 but with #60 and #61 applied)
I understand now, that does appear to be the issue, I hadn't caught that detail in the docs. This might be worth a big red flag in the docs.
@mrk-its your PR is brilliant, it solved my next problem too. I was doing a test to see if I could open a large file (3+ GB) and only read the first few bytes of its header. With fs_s3fs_ng it worked no problem, but with fs_s3fs with strict=False I was able to open the file it appears, but it started reading the entire file in.
I'll watch your PRs, you've got my vote for sure! :)
Activity
mrk-its commentedon Nov 17, 2019
Could you try to reproduce this using code from #60? (you can simply install
fs-s3fs-ngpackage - it is the same as fs-s3fs==1.1.1 but with #60 and #61 applied)willmcgugan commentedon Nov 17, 2019
@davidparks21 Did you create the test directory with S3FS?
S3FS has some limitations, which are documented here.
davidparks21 commentedon Nov 17, 2019
I understand now, that does appear to be the issue, I hadn't caught that detail in the docs. This might be worth a big red flag in the docs.
@mrk-its your PR is brilliant, it solved my next problem too. I was doing a test to see if I could open a large file (3+ GB) and only read the first few bytes of its header. With
fs_s3fs_ngit worked no problem, but withfs_s3fswithstrict=FalseI was able to open the file it appears, but it started reading the entire file in.I'll watch your PRs, you've got my vote for sure! :)