From 29df4e75bf1b5006b34f5f6421dd20de071fbcd2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 25 Feb 2020 13:22:46 -0400 Subject: [PATCH] response --- ..._8b066ad9628073a3ae045087b4ea79b5._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/forum/WrongRequestBodyStreamSize_exporting_large_file_to_S3/comment_1_8b066ad9628073a3ae045087b4ea79b5._comment diff --git a/doc/forum/WrongRequestBodyStreamSize_exporting_large_file_to_S3/comment_1_8b066ad9628073a3ae045087b4ea79b5._comment b/doc/forum/WrongRequestBodyStreamSize_exporting_large_file_to_S3/comment_1_8b066ad9628073a3ae045087b4ea79b5._comment new file mode 100644 index 0000000000..665cb9118a --- /dev/null +++ b/doc/forum/WrongRequestBodyStreamSize_exporting_large_file_to_S3/comment_1_8b066ad9628073a3ae045087b4ea79b5._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-02-25T16:47:29Z" + content=""" +How large, in bytes, is the file you were trying to upload there, +and what was the partsize? + +WrongRequestBodyStreamSize is an exception from the http-client +library. It throws this when writing a request to the http server +and the stream of data included in the request somehow does not have the +length it expected. + +It expected 31419314 bytes and got only 29814466, and this appears +to have been the last part of the file. + +Looking at the http-client code, it seems almost certainly due to a +RequestBodyStream declaring an incorrect length of the stream. And, +git-annex does use RequestBodyStream in particular in S3 multipart uploads. +So it seems most likely a git-annex bug. +"""]]