diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-05-28 00:33:48 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-05-28 00:33:48 +0000 |
| commit | 490091cb3a9e42d82d3e07e6c85653ec0dafc4e2 (patch) | |
| tree | d2eedd8ce3c18e8cb136085969d4d8af58db26d3 /doc/bugs/Truncated_file_transferred_via_S3 | |
| parent | e9745a85b72d43d57b6cba64c7062c49dc65c675 (diff) | |
Added a comment
Diffstat (limited to 'doc/bugs/Truncated_file_transferred_via_S3')
| -rw-r--r-- | doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment new file mode 100644 index 000000000..b5c27c5fd --- /dev/null +++ b/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.176" + subject="comment 6" + date="2014-05-28T00:33:48Z" + content=""" +I've just noticed the the S3 backend used Char8 for reading/writing encrypted files. I don't know that this could result in this problem, but it at least seems possible. If you can still reproduce the bug, try getting the next daily build and see if perhaps it fixed it. +"""]] |