From 723c4f3edcaa2aa5a356ac581f7ec7ddcb436f02 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 28 May 2014 00:33:48 +0000 Subject: [PATCH] Added a comment --- .../comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment 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 0000000000..b5c27c5fde --- /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. +"""]]