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

Bugfix to getting content from an export remote with -J, when the export database was not yet populated.

Browse source
This commit is contained in:
Joey Hess 2020-02-26 14:57:29 -04:00
parent cb86caf929
commit e520341500
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 37 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/fails_to___96__get__96___in_parallel_for_a_freshly_clone_from_public_s3_bucket_where_versioning_info_was_forgotten.mdwn
View file

@ -89,3 +89,5 @@ get sub-01/meg/sub-01_task-audiovisual_run-01_meg.fif (from s3-PUBLIC...)
[[!meta author=yoh]]
[[!tag projects/repronim]]
> [[fixed|done]] --[[Joey]]

18
doc/bugs/fails_to___96__get__96___in_parallel_for_a_freshly_clone_from_public_s3_bucket_where_versioning_info_was_forgotten/comment_4_4a4d5b62af4a42ab9072ccaa6d8bed7d._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-02-26T18:22:46Z"
content="""
How do I produce such a repo, I thought that git-annex has fixed the
problem that made it not include the S3 versioning information?
I don't want to see a lot of repos being created with that information
missing.
----
Anyway, the S3 version is is a red herring, the failure is actually
caused by the export db not getting populated from the git-annex branch
before some threads try to use it. Remote.Helper.ExportImport has a
updateexportdb that lets one thread update the db, but other threads
don't block waiting for it. Easily fixed.
"""]]