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

comment

Browse source
This commit is contained in:
Joey Hess 2020-12-10 17:52:26 -04:00
parent 8c0ff6b8cd
commit 108c7d96dd
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/export_-J_6__to_S3__58___transfer_already_in_progress/comment_1_f81e00b5293f2df894dc3cd1678530c1._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-12-10T21:49:03Z"
content="""
Answer first: Re-running export will skip over things that it knows
it already exported before, so should be efficient.
Yes, it seems this is the same as the old issue where 2 files with the same
key being sent to a remote concurrently failed like this. Fixed back then by
skipping the second, redundant transfer. But in this case, since there are
2 files on the remote, the data needs to be sent twice. So it probably just
shouldn't guard against redundant transfers when exporting. Or if it does,
it should use the ExportLocation, not the Key as what coulds as redundant..
I will have to look at this later though.
"""]]