mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2020-01-23 15:33:41 -04:00
parent 342ff4666c
commit 07a8d6dd65
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/fails_to___96__get__96___in_parallel_for_a_freshly_clone_from_public_s3_bucket_where_versioning_info_was_forgotten/comment_1_917b46d9ca69c4e8181d041d5414d373._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-01-23T19:26:20Z"
content="""
Looking in the git-annex branch of this repository, for information about
a key such as MD5E-s10555001--f8bc87e8841634b3d2f9ac0ba85d0a83.nii.gz.log
which is one of the files that fails to download, all there is is this:
joey@darkstar:/tmp/ds000248#git-annex>cat ./f0b/978/MD5E-s10555001--f8bc87e8841634b3d2f9ac0ba85d0a83.nii.gz.log
1531766688.020213886s 1 82a4b182-753f-4d93-a59e-20cfdd4d4237
1531766681.703832952s 1 e3612a8a-0c48-4374-9bfb-888f4010be54
So location log says it's in s3-PUBLIC, but in fact no S3 version id has been recorded.
And there were old bugs that prevented the recording of the S3 version id.
Notably, it used to be possible to set versioning=yes on an existing S3
remote, and the files already stored in it necessarily lacked version ids
then. That has been fixed.
So, is it still possible to reproduce creating a repository with this problem?
"""]]