VS Code can't clone nrf connect SDK

RE: VS Code can't clone nrf connect SDK

Senura — Mon, 15 Jan 2024 08:27:53 GMT

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.

RE: VS Code can't clone nrf connect SDK

Senura — Fri, 12 Jan 2024 10:46:19 GMT

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

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Fri, 12 Jan 2024 07:56:49 GMT

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.

RE: VS Code can't clone nrf connect SDK

Senura — Fri, 12 Jan 2024 07:53:08 GMT

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.

RE: VS Code can't clone nrf connect SDK

Hung Bui — Thu, 04 Jan 2024 10:19:55 GMT

Thanks for the report Syed. I will forward it to the team.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Wed, 03 Jan 2024 15:10:34 GMT

also if you can update the documentation on the choco list -lo because the -lo argument has been removed from chocolatey.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Wed, 03 Jan 2024 15:08:07 GMT

My internet is pretty stable I have cloned a good number of repositories and downloaded other stuff as well without any problems. So maybe there is something that can be improved from your side. Thank you Hung Bui for your assistance I will try to find some other network and install the SDK.

RE: VS Code can't clone nrf connect SDK

Hung Bui — Wed, 03 Jan 2024 13:58:05 GMT

Thanks, I will let you know if we find any problem. But from what you described, it's quite clear that the issue is related to your network.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Wed, 03 Jan 2024 13:57:52 GMT

well this time it passed the west init line but now it gives error on west update.

c:\ncs>west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.5.0
=== Initializing in c:\ncs
--- Cloning manifest repository from https://github.com/nrfconnect/sdk-nrf, rev. v2.5.0
Cloning into 'c:\ncs\.west\manifest-tmp'...
remote: Enumerating objects: 200532, done.
remote: Counting objects: 100% (140/140), done.
remote: Compressing objects: 100% (82/82), done.
remote: Total 200532 (delta 61), reused 116 (delta 58), pack-reused 200392
Receiving objects: 100% (200532/200532), 133.38 MiB | 450.00 KiB/s, done.

Resolving deltas: 100% (150050/150050), done.
Note: switching to '1fae141fc6713dd331b797fc96c90dc84552242d'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

Updating files: 100% (8085/8085), done.
--- setting manifest.path to nrf
=== Initialized. Now run "west update" inside c:\ncs.

c:\ncs>west update
=== updating zephyr (zephyr):
--- zephyr: initializing
Initialized empty Git repository in C:/ncs/zephyr/.git/
--- zephyr: fetching, need revision v3.4.99-ncs1
remote: Enumerating objects: 927552, done.
remote: Counting objects: 100% (92/92), done.
remote: Compressing objects: 100% (58/58), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 3336 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: fetch -f --tags -- https://github.com/nrfconnect/sdk-zephyr v3.4.99-ncs1

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Wed, 03 Jan 2024 13:42:38 GMT

here is the full log

Microsoft Windows [Version 10.0.19045.3803]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>choco feature enable -n allowGlobalConfirmation
Chocolatey v2.2.2
Nothing to change. Config already set.

C:\Windows\system32>choco install cmake --installargs 'ADD_CMAKE_TO_PATH=System'
Chocolatey v2.2.2
Installing the following packages:
cmake
By installing, you accept licenses for the packages.
cmake v3.27.9 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

Chocolatey installed 0/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Warnings:
 - cmake - cmake v3.27.9 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

C:\Windows\system32>choco install ninja gperf python git dtc-msys2 wget unzip
Chocolatey v2.2.2
Installing the following packages:
ninja;gperf;python;git;dtc-msys2;wget;unzip
By installing, you accept licenses for the packages.
ninja v1.11.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
gperf v3.1.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
python v3.12.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
git v2.43.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
dtc-msys2 v1.5.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
Wget v1.21.4 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
unzip v6.0.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

Chocolatey installed 0/7 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Warnings:
 - dtc-msys2 - dtc-msys2 v1.5.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - git - git v2.43.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - gperf - gperf v3.1.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - ninja - ninja v1.11.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - python - python v3.12.1 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - unzip - unzip v6.0.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.
 - Wget - Wget v1.21.4 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

C:\Windows\system32>choco list -lo
Chocolatey v2.2.2
Invalid argument -lo. This argument has been removed from the list command and cannot be used.

C:\Windows\system32>choco list all
Chocolatey v2.2.2
chocolatey 2.2.2
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
cmake 3.27.9
cmake.install 3.27.9
git 2.43.0
git.install 2.43.0
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
ninja 1.11.1
python 3.12.1
python3 3.12.1
python312 3.12.1
vcredist140 14.38.33130
vcredist2015 14.0.24215.20170201
Wget 1.21.4
19 packages installed.

C:\Windows\system32>pip3 install west
Requirement already satisfied: west in c:\python312\lib\site-packages (1.2.0)
Requirement already satisfied: colorama in c:\users\hamza\appdata\roaming\python\python312\site-packages (from west) (0.4.6)
Requirement already satisfied: PyYAML>=5.1 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from west) (6.0.1)
Requirement already satisfied: pykwalify in c:\users\hamza\appdata\roaming\python\python312\site-packages (from west) (1.8.0)
Requirement already satisfied: setuptools in c:\users\hamza\appdata\roaming\python\python312\site-packages (from west) (69.0.3)
Requirement already satisfied: packaging in c:\users\hamza\appdata\roaming\python\python312\site-packages (from west) (23.2)
Requirement already satisfied: docopt>=0.6.2 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from pykwalify->west) (0.6.2)
Requirement already satisfied: python-dateutil>=2.8.0 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from pykwalify->west) (2.8.2)
Requirement already satisfied: ruamel.yaml>=0.16.0 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from pykwalify->west) (0.18.5)
Requirement already satisfied: six>=1.5 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from python-dateutil>=2.8.0->pykwalify->west) (1.16.0)
Requirement already satisfied: ruamel.yaml.clib>=0.2.7 in c:\users\hamza\appdata\roaming\python\python312\site-packages (from ruamel.yaml>=0.16.0->pykwalify->west) (0.2.8)

[notice] A new release of pip is available: 23.2.1 -> 23.3.2
[notice] To update, run: python.exe -m pip install --upgrade pip

C:\Windows\system32>cd c:/

c:\>cd ncs

c:\ncs>dir
 Volume in drive C has no label.
 Volume Serial Number is 8063-56D3

 Directory of c:\ncs

01/03/2024  06:27 PM    <DIR>          .
01/03/2024  06:27 PM    <DIR>          ..
01/03/2024  10:06 AM    <DIR>          downloads
01/03/2024  10:13 AM    <DIR>          tmp
01/03/2024  10:13 AM    <DIR>          toolchains
               0 File(s)              0 bytes
               5 Dir(s)  20,783,288,320 bytes free

c:\ncs>dir
 Volume in drive C has no label.
 Volume Serial Number is 8063-56D3

 Directory of c:\ncs

01/03/2024  06:37 PM    <DIR>          .
01/03/2024  06:37 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s)  20,783,157,248 bytes free

c:\ncs>west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.3.0
=== Initializing in c:\ncs
--- Cloning manifest repository from https://github.com/nrfconnect/sdk-nrf, rev. v2.3.0
Cloning into 'c:\ncs\.west\manifest-tmp'...
remote: Enumerating objects: 200532, done.
remote: Counting objects: 100% (139/139), done.
remote: Compressing objects: 100% (81/81), done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
error: 10595 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.3.0 https://github.com/nrfconnect/sdk-nrf 'c:\ncs\.west\manifest-tmp'

RE: VS Code can't clone nrf connect SDK

Hung Bui — Wed, 03 Jan 2024 12:24:50 GMT

Please post the full log including the error.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Wed, 03 Jan 2024 11:41:00 GMT

I followed the same method as shown in https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.3.0/nrf/getting_started/installing.html link. I have and the error occurs at the line

west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.3.0

before this all the steps went smooth with no errors at all. When this command is executed it starts and reaches to the line Receiving objects and then after downloading something like 30 MBs ends with the error that I initially posted.

I borrowed another friend PC remotely for sometime and downloaded SDK with VS code and it worked without errors, the network is different and also it has windows 11 while on my pc I have windows 10.

Hope that helps in finding the cause of the problem.

RE: VS Code can't clone nrf connect SDK

Hung Bui — Wed, 03 Jan 2024 10:11:43 GMT

Hi Syed,
We don't provide the .zip file for NCS and most likely you will need to install other dependencies to be able to use it.
I have forwarded the issue to our team, I will let you know if we find anything.
Could you please send us the full log on the step by step manual installation that you have done until you see the error.

Have you tried to do installing from another network ?

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Tue, 02 Jan 2024 15:12:19 GMT

This is what I get when trying with toolchain manager from nrf connect desktop.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Tue, 02 Jan 2024 10:39:33 GMT

Is it possible that someone else download this for and then make a zip file of the ncs folder and share with me. and I then extract the file in my C:\ folder, will this work with VS code nrf connect extension?

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Tue, 02 Jan 2024 10:35:54 GMT

I tried with the toolchain manager but no luck, same error occurs. It stops at the west init -m github.com/.../sdk-nrf --mr v2.4.2 as shown in the video that you just shared.

RE: VS Code can't clone nrf connect SDK

Hung Bui — Tue, 02 Jan 2024 10:31:17 GMT

Hi Syed,
I'm not sure why you get the error. But a quick search pointed me to this video: https://www.youtube.com/watch?v=UFhiF3IzbUw

The poster has the same issue as yours and he managed to get around by using a different network.

In your case it seems that you had the same issue even with a different network ?

Could you try to test using nRF Connect for Desktop -> Toolchain manager ?

If you do installing manually, at which step did it stop ?

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Tue, 02 Jan 2024 09:41:09 GMT

My internet connection is not that bad it works fine if I clone other repositories without west. But when using west this problem occurs.

Here are some pictures of my internet connection speed.

I borrowed a friend's PC and tried with the fiber optic connection which is much faster than my connection but I still got the same problem on his PC. Does someone wants to help out in this regard?

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Mon, 01 Jan 2024 09:32:44 GMT

Even with the manual install method and doing a clean re installation of VS Code I still get the same error.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Mon, 01 Jan 2024 05:44:11 GMT

I have a second pc with Ubuntu, so I did a clean install on my Ubuntu pc last night but same error popped up. Looks like network issue maybe. But I don't know I have fine internet speed.

RE: VS Code can't clone nrf connect SDK

mouthbreather — Sun, 31 Dec 2023 18:43:47 GMT

Maybe try out installing it manually:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.3.0/nrf/getting_started/installing.html

Also I dont know if the extension in VSCode will pick it up. Definetly restart VSCode after manual installation. And hit the "circle arrow" next to "Manage SDK…".

If you did not have VSCode installed before it might be wise just to start all over. Or maybe create a new user on your computer and do a clean installation of vscode, nordic extension and then continue with toolchain and sdk.

RE: VS Code can't clone nrf connect SDK

mirhamza708 — Sun, 31 Dec 2023 18:19:37 GMT

When click on Manage SDK there only two options
>install SDK
>create west workspace

Install doesn't work and I have no idea how to use the second option.

RE: VS Code can't clone nrf connect SDK

mouthbreather — Sun, 31 Dec 2023 18:14:47 GMT

Hi there,

quick search on the net showed the http/2 might be the problem or the post buffer of git not beeing big enough. Also if on VPN try turning it off. As I dont know how to change the settings of git within VSCode, I cant help you there.

But you could just clone the repo (or download it by hand) and then tell NRF Connect where you downloaded it:

- Open Extension
- Click on Manage SDK
- Set Active SDK
- Enter directory or choose from dropdown.

Hope that helps.