diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-10-23 21:05:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-10-23 21:05:15 +0000 |
| commit | 6a910838518f83980733e5af278da2ee4a1395fc (patch) | |
| tree | a5f72239adc2a404cafe4d4c652dff94c8c44980 | |
| parent | 9e33f1b88503eae29797f171ba219cba1f34325a (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/Upload_to_S3_fails_/comment_11_65cb9b1dd69cd657f2cfde036eb60417._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/Upload_to_S3_fails_/comment_11_65cb9b1dd69cd657f2cfde036eb60417._comment b/doc/bugs/Upload_to_S3_fails_/comment_11_65cb9b1dd69cd657f2cfde036eb60417._comment new file mode 100644 index 000000000..ec59d6a20 --- /dev/null +++ b/doc/bugs/Upload_to_S3_fails_/comment_11_65cb9b1dd69cd657f2cfde036eb60417._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.96" + subject="comment 11" + date="2014-10-23T21:05:15Z" + content=""" +When it resumes, it will start at 0% but jump forward to the resume point pretty quickly, after verifying which chunks have already been sent. +If any full chunk gets transferred, I'd expect it to resume. This may not be very obvious it's happening for smaller files. + +I have been running `git annex testremote` against S3 special remotes today, and have not managed to reproduce this problem (using either the old S3 or the new AWS libraries). It could be anything, including a problem with your network or the network between you and the S3 endpoint. Have you tried using a different S3 region? +"""]] |