-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
dvc pull
does not seem to work for files whose md5 starts with 00
#4141
Comments
@jnd77 thanks for the bug report. Could you post the rest of your verbose output (linking a gist or something would be fine)? Bug is most likely something causing us to drop the hashes fetched during remote size estimation after: Line 816 in 00c135f
|
Thanks @pmrowla to have suck a quick look. I reran with --verbose.
|
I have run this within a simple Docker container:
|
Issue is that for S3 Lines 189 to 190 in 07da9f1
This breaks behavior when we try to walk 3-character prefixes like Being able to walk arbitrary-length prefixes is useful (for remotes that support it). So I think we should probably explicitly append trailing slashes before calling This was not an issue before the 1.x remote tree refactor because we had the separate (but essentially duplicated) |
Thanks guys. :) |
Bug Report
Please provide information about your setup
Output of
dvc version
:1.1.1
Additional Information (if any):
When I run
dvc pull
on a repo with around 500+ items, all but 4 are retrieved successfully .I have noticed these 4 files all have a md5 starting with
00
and therefore are in a folder called00
in their S3 bucket.(these 4 files are also the only ones in that folder)
Finally, it works fine if I revert back to 0.90.2 version.
The text was updated successfully, but these errors were encountered: