It seems like you're encountering network-related issues while updating large Git repositories over WiFi. The error message "RPC failed; curl 92 HTTP/2 stream 7 was not closed cleanly: CANCEL (err 8)" indicates a problem with the network connection during the fetch operation.
Here are a few things you can try to resolve this issue: 1 Check Network Stability: Ensure that your WiFi connection is stable and has a strong signal. You might want to try connecting via a wired Ethernet connection if possible, to rule out any WiFi-related issues. 2. Update Git and Dependencies: Make sure you have the latest version of Git installed. Additionally, check if there are any updates for related dependencies or libraries that Git relies on. 3. Increase Timeout Settings: You can try increasing the timeout settings for Git operations. For example, you can set a higher timeout value using `git config --global http.lowSpeedLimit 5000` (adjust the value as needed). 4 .Use SSH Protocol: Instead of HTTPS, consider using the SSH protocol for Git operations. This can sometimes provide a more stable connection. 5. Check Firewall and Proxy Settings: Ensure that there are no firewall or proxy settings interfering with your Git operations. Or You can force git using http version 1.1 git config --global http.version HTTP/1.1 On Fri, 3 May, 2024, 11:50 pm Riccardo Mottola, <riccardo.mott...@libero.it> wrote: > Hi, > > I'm updating fairly big git repositories (e.g. mozilla and similar) and > continue getting these errors. I am over a fast WiFi. > > e$ git pull > remote: Enumerating objects: 4822, done. > remote: Counting objects: 100% (4822/4822), done. > remote: Compressing objects: 100% (1027/1027), done. > error: RPC failed; curl 92 HTTP/2 stream 7 was not closed cleanly: > CANCEL (err 8) > error: 5970 bytes of body are still expected > fetch-pack: unexpected disconnect while reading sideband packet > fatal: early EOF > fatal: fetch-pack: invalid index-pack output > > I can insist as much as I want, different byte count expected, but I am > unable to finish the operation. Being github, it is a decently reliable > server... and on other systems I don't have this issue. > I don't remember having many issues with 9.3, but maybe it is a mix of > network and kernel. > > Riccardo >
