mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
gioele@678b7c03f524f2669b179b603f65352fcc16774e 2025-07-09 19:36:24 +00:00 • committed by admin
parent 98b7cf3ac4
commit 072f2606a1
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/error_during_copy_to_S3/comment_4_6c2bcd8f475459e76aed9a5ea6661641._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="gioele@678b7c03f524f2669b179b603f65352fcc16774e"
nickname="gioele"
avatar="http://cdn.libravatar.org/avatar/366dbda84e78aff8a8a070622aeb63ce"
subject="comment 4"
date="2025-07-09T19:36:24Z"
content="""
For the record, I've experienced a similar problem when uploading a 11 GB file to Backblaze B2:
> 6:1 (158)-6:8 (165): Expected end element for: Name {nameLocalName = \"hr\", nameNamespace = Nothing, namePrefix = Nothing}, but received: EventEndElement (Name {nameLocalName = \"body\", nameNamespace = Nothing, namePrefix = Nothing})
Using `git annex copy --explain` shows that the remote provided a more useful error message:
> 1% 116.47 MiB 5 MiB/s 38m9s
>
> [22:57:03.01203742] (Remote.S3) Response status: Status {statusCode = 413, statusMessage = \"Request Entity Too Large\"}
Maybe the status code could be inspected before parsing the body of the response to provide a clearer error message?
"""]]