VS Code can't clone nrf connect SDK

[mirhamza708]

I am learning development with nrf connect sdk. I installed vs code and in vs code downloaded the nrf connect for vs code extension pack, everything downloads well. On the nrf connect extension menu I go to download toolchain and the toolchain installs okay. but then downloading SDK always throws this error.

The error codes are as follows

 

[00:39:13] Command failed: west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.4.2
Cloning into 'c:\ncs\v2.4.2\.west\manifest-tmp'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
error: 4674 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
FATAL ERROR: command exited with status 128: git clone --branch v2.4.2 https://github.com/nrfconnect/sdk-nrf 'c:\ncs\v2.4.2\.west\manifest-tmp'

Please help I am stuck on this for 2 days now.
Thanks in advance.

[Senura]

I am also getting the same issue. Any answer for this? This isn't a network problem since I keep getting the same error even though I tried with different networks.

[mirhamza708]

I went to a friend's place and used his internet to get it to work. But this is not just a network problem, it's the way they keep the repository which is causing the problem. Hope they fix it soon.

[Senura]

I tried with three new internet connections but the same issue happened every time.

[Senura]

This issue appears to be related to network speed problems. I successfully installed it during off-peak hours, around midnight. However, when the network is unstable and the speed drops below 15Mbps, the repository cloning process fails. I suspect Nordic has integrated some features in the tool manager to terminate the cloning after a few unsuccessful attempts. I hope that they address this issue, considering that internet speed varies in different parts of the world. Interestingly, I haven't faced a similar problem when using Github, indicating that it might be specific to the tool manager software.