Not able to install edge-impulse-cli in linux - Help

相关文章推荐

逃课的茶壶 · Microsoft Edge 开发工具协议 ...· 3 月前 ·

痛苦的菠萝 · 2020水业十大影响力企业等11大榜单出炉- ...· 2 月前 ·

神勇威武的红豆 · 中国特色的收费公路政策功不可没-媒体报道-中 ...· 11 月前 ·

想出家的电梯 · 2023年ISEF竞赛国家队名单公布！ - ...· 1 年前 ·

小胡子的松鼠 · 无法初始化MockMaker-腾讯云开发者社 ...· 2 年前 ·

小眼睛的课本 · Perform an in-place ...· 2 年前 ·

I have tried installing edge-impulse-cli but I have been getting the following error in Linux

npm WARN deprecated @zeit /dockerignore@0.0.5: “ @zeit /dockerignore” is no longer maintained
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.4: request-promise has been deprecated because it extends the now deprecated request package, see http.s://github.com/request/request/issues/3142
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https.://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https.://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. ( ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub )
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See h-ttps://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142

friend, I think the messages indicate that you need to upgrade some libraries, another way out is to use a virtual machine with a recommended distro and try to run tests.

I don’t like dealing with many dependencies, but anyone who works with Linux needs to get used to it.

Hello @melta101 ,

I don’t think those are errors, they are warnings.

Can you check if you see something like that at the end of the installation:

+ edge-impulse-cli@1.21.1
added 377 packages from 266 contributors in 10.947s
That would indicate it has been successfully installed.
Best,
Louis
          i have gotten the following output upon using the npm installation command
npm WARN deprecated @zeit/dockerignore@0.0.5: “@z.eit/dockerignore” is no longer maintained

npm WARN deprecated h.ar-validator@5.1.5: this library is no longer supported

npm WARN deprecated request-promise@4.2.4: request-promise has been deprecated because it extends the now deprecated request package, see https://.github.com/request/request/issues/3142

npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub)

npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (http.s://github.com/visionmedia/debug/i.ssues/797)

npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (h.ttps://github.com/visionmedia/debug/issues/797)

npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See There’s Math.random(), and then there’s Math.random() · V8 for details.

npm WARN deprecated request@2.88.0: request has been deprecated, see ht.tps://github.com/request/request/issues/3142
changed 378 packages in 30s
doesn’t seem like it for installed
          @melta101 It looks like the EdgeImpulse CLI was already installed, so you get a slightly different message than what Louis stated.
Does edge-impulse-daemon --version return a version number?
          I just verified on Widows 10 that the EdgeImpulse CLI does not like node.js versions:
v14.21.3
v20.6.0
I could only get the EI CLI to install under node v18.7.1.
What does node -v return?
          So I got the EI CLI to run under node.js v20.
The following worked for v20.6.0 but not v14.21.3 on Windows 10. I am not sure all of the following is needed but it worked for me.
Uninstall everything node.js related:
npm -g uninstall node-gyp
npm uninstall -g edge-impulse-cli
Uninstall node.js from Add/Remove Programs
Delete folder %programfiles%\nodejs
Delete folder %appdata%\npm
Delete folder %appdata%\npm-cache
I removed all Pythons including Miniconda3 leaving only one:
py --list-paths	# Show all Pythons
I left C:\Python311
Remove folder C:\ProgramData\chocolatey
Remove folder C:\ProgramData\ChocolateyHttpCache
Remove all node.js related Environment Variables and Paths
To do so, hit “Start” and search for “Environment Variables”
Remove anything related to System variables chocolatey, npm, nvm and node
Edit your PATH and remove everything that references chocolatey, npm, nvm and node
Make sure the PATH has a reference to your singleton Python folder
Cold boot
Official installer here: Download | Node.js
Execute node-v20.6.0-x64.msi
node -v
v20.6.0