Attempting to clone a large repository from GitHub.com wth HTTPS over Tor often fails before the clone completes. However cloning with authenticated SSH over Tor seems to have a higher chance of success.
remote: Enumerating objects: 10227095, done.
remote: Counting objects: 100% (8/8), done.
remote: Compressing objects: 100% (6/6), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 2874 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
Anyone else have a similar experience?
On second thought this is probably more suited for ‘General Discussion’ category.
I conducted tests of cloning large Git repositories from other Git hosts with HTTPS over Tor and did not encounter the same issue. So it is likely an issue with GitHub.com. Unfortunate.
1 Like
To follow up on this. I found a discussion of a similar issue on the GitHub community forum and it appears this issue may be because of slow connections (<1MB/s) and may not be an issue with Tor usage per se. Unfortunately GitHub staff do not actively monitor that forum and attempts by others at contacting customer support have not led to a resolution.
Perhaps if others encounter this issue they could also contact GitHub support and note down the mentioned ticket numbers to attempt to obtain priority for this issue.