New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension v1.6.0 'Command not found' error - but works with extension v1.5.1. (VSC-1063) #907
Comments
I'm also getting OS Operating System version Visual Studio Code version EDIT: solved by downgrading to |
Thanks for the report - it seems this bug is universal: Similar issue on MacOS |
All commands fails with message 'Command not found' |
Could you try this vsix installer to see if the issue is fixed ? |
@brianignacio5, tried your vsix, still getting the following errors configure ESP-IDF extension
and when trying to create project from extension template:
|
Can you share the extension log or other related troubleshoot information? Windows: Same error as before or different one ? |
Also issue for me. Clicking on anything from the ESP-IDF plug-in or running commands result in ESP-IDF version 5.0.1 |
Have you tried the new vsix installer @windorey @parksj10 ? Could you try this vsix installer to see if the issue is fixed ? Can you share the extension log or other related troubleshoot information? Windows: %USERPROFILE%.vscode\extensions\espressif.esp-idf-extension-VERSION\esp_idf_vsc_ext.log Same error as before or different one ? |
@brianignacio5 the latest |
Hi. I have the same problem on MacOS and Linux. What I figured out is that you can't run any command when you are on any other project than esp-idf based. When you open any esp-idf project, then you can run any command without any problem. It seems that extension is looking for CMakeList.txt for some reason:
|
Did you try the latest vsix installer I share before @bartoszwalicki ? I'll take a look @parksj10 |
@brianignacio5 tried vsix installer that you shared. Everything working. |
It seems that extension is looking for CMakeList.txt for some reason:
I was trying to play with the VSCode extension yesterday and was banging my head against the wall. I think the above error is central: starting vscode with the IDF extension (1.6.0) installed needs to be started in an IDF project directory initially. This is annoying, e.g. if you want to run "Create Project" or "Create Component" It seems to me, that a workaround is |
Have you tried the Installer above to see if the issue is fixed ? |
It seems to have fixed the problem. I don't really use vs code though, so I have no idea what I'm doing. Thanks! Details:
repeated the above with the 1.6.0 network install, last step fails with "Command not found". Uninstalling the vsix only via the Extension manager does repoduce the original problem, presumably because the orphaned |
For completeness, marking this reported issue as fixed for me in IDF VSCode extension 1.6.1, with VSCode 1.77.3, Kubuntu 23.04. |
That is the only correct guide that works for me. Thanks a lot! |
OS
Linux
Operating System version
Kubuntu 22.10
Visual Studio Code version
1.76.1
ESP-IDF version
5.0.1
Python version
3.10.7
Doctor command output
Doctor fails to launch with 'Command not found'.
Extension
[root project directory] is my system's path to projects.
{"message":"Cannot access filePath: [root project directory]/Arduino/XIAO-ESP32-test/CMakeLists.txt","stack":"Error: ENOENT: no such file or directory, access '[root project directory]>
Description
'Command not found' when invoking any ESP-IDF extension command.
Debug Message
Other Steps to Reproduce
Following the 'CMakeLists.tst' not found error, I added one to the project and the extension still fails to run any command.
I have also tried re-installing the extension, removing config, etc. However, v1.5.1 of the extension has no problems with any installation config situation.
The issue has been mentioned by other users, e.g. : Command not found.
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: