I frequently get an error when cloning a large repository from GitHub (specifically, Chromium, but it doesn't matter) on my local network, after downloading about ~10 GB:
git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress https://github.com/chromium/chromium
Cloning into '<path to dir>'...
remote: Enumerating objects: 15975048, done.
remote: Counting objects: 100% (6505/6505), done.
remote: Compressing objects: 100% (3237/3237), done.
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
I read up on several StackOverflow questions with the same issue[0][1][2] - the issue seems to be related to the network being slow/unstable (note that I tried increasing git buffer size but that didn't help). It seems to be a local network issue, which I confirmed by going to a different network and being able to do a successful git clone.
I'd like to resolve this. My confusion: I'm pretty sure my internet speed is fine: I'm able to get 100 Mbps according to Google's M-Lab internet speed test. If it's simply a question of increasing my internet speed, I can pay more and get on a better plan with my current ISP, but I want to confirm that the issue is actually because of speed (I'm not sure why it would be - why would git clone or rather curl give up because of slow speed? I'm happy for it to take a long time as long as it does complete). If it's not a question of speed, but rather stability, what would be a good way to diagnose this so I can take that info to my ISP? I called up my ISP and they have no clue why a long-running curl command would be failing. I'm able to download the zip from https://github.com/chromium/chromium/releases without it failing.
