This bites us as well. Identical issue to Dan Carleton back in 2010 - our duplicity-full-signatures is a little over 5GB, and S3 gives us a broken pipe retry after retry until we fail.
Has anyone found a workaround in the multipart parameters or timeouts for this? And I take it this was not fixed in 0.6.23 since I'm running 0.6.24?
Great package otherwise, thanks for the work on it, but this issue is a deal breaker for us at the moment.
This bites us as well. Identical issue to Dan Carleton back in 2010 - our duplicity- full-signatures is a little over 5GB, and S3 gives us a broken pipe retry after retry until we fail.
Has anyone found a workaround in the multipart parameters or timeouts for this? And I take it this was not fixed in 0.6.23 since I'm running 0.6.24?
Great package otherwise, thanks for the work on it, but this issue is a deal breaker for us at the moment.