Skip to content

Esp-Idf extension fails to setup already existing setup and just re-downloads the entire setup (VSC-1720) #1600

Open
@Platin21

Description

@Platin21

OS

MacOS

Operating System version

macOS 15.5

Visual Studio Code version

1.101.1 (Universal) Commit: 18e3a1ec544e6907be1e944a94c496e302073435

ESP-IDF version

4.5.x

Python version

3.13.3

Doctor command output

doctor_cmd.txt

Extension

Command failed: /Users/platin21/esp/v5.3.1/esp-idf/tools/python_env/idf5.3_py3.11_env/bin/python /Users/platin21/esp/v5.4/tools/check_python_dependencies.py -r /Users/platin21/esp/v5.4/tools/requirements/requirements.core.txt
The following Python requirements are not satisfied:
Error while checking requirement 'psutil'. Package was not found and is required by the application: No package metadata was found for psutil
To install the missing packages, please run "install.sh"
Diagnostic information:
IDF_PYTHON_ENV_PATH: /Users/platin21/.espressif/python_env/idf5.4_py3.13_env
Python interpreter used: /Users/platin21/esp/v5.3.1/esp-idf/tools/python_env/idf5.3_py3.11_env/bin/python
Warning: python interpreter not running from IDF_PYTHON_ENV_PATH
PATH: /Users/platin21/esp/v5.4/components/espcoredump:/Users/platin21/esp/v5.4/components/partition_table:/Users/platin21/esp/v5.4/components/app_update:/Users/platin21/.espressif/tools/xtensa-esp-elf-gdb/14.2_20240403/xtensa-esp-elf-gdb/bin:/Users/platin21/.espressif/tools/riscv32-esp-elf-gdb/14.2_20240403/riscv32-esp-elf-gdb/bin:/Users/platin21/.espressif/tools/xtensa-esp-elf/esp-14.2.0_20241119/xtensa-esp-elf/bin:/Users/platin21/.espressif/tools/riscv32-esp-elf/esp-14.2.0_20241119/riscv32-esp-elf/bin:/Users/platin21/.espressif/tools/esp32ulp-elf/2.38_20240113/esp32ulp-elf/bin:/Users/platin21/.espressif/tools/openocd-esp32/v0.12.0-esp32-20241016/openocd-esp32/bin:/Users/platin21/.espressif/python_env/idf5.4_py3.13_env/bin:/Users/platin21/esp/v5.4/tools:/opt/homebrew/opt/openjdk/bin:/opt/homebrew/opt/llvm/bin:/opt/homebrew/Cellar/llvm/17.0.5/bin/:/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/:/Users/platin21/Documents/Odin:/Users/platin21/Documents/xtensa-llvm/build/bin/:/opt/homebrew/opt/openjdk/bin:/opt/homebrew/opt/llvm/bin:~/Documents/lldbg/bin:/Users/platin21/Documents/Odin:/opt/homebrew/opt/openjdk/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/platin21/Library/Application Support/JetBrains/Toolbox/scripts
Command failed: /Users/platin21/esp/v5.3.1/esp-idf/tools/python_env/idf5.3_py3.11_env/bin/python /Users/platin21/esp/v5.4/tools/check_python_dependencies.py -r /Users/platin21/esp/v5.4/tools/requirements/requirements.core.txt

This all makes zero sense as in the terminal it just works, i also dunniowhy i see the wrong python virtual env as i selected the one for the v5.4 version

Description

I seemingly always encounter the issue that the idf-extension doesn't want to take the version of idf i already have installed without it. Somehow it always even if the path is correctly set fails to just use the version.
I always seem to get a new download even though i already have everything installed.

i dunno if this also breaks my idf setup in the terminal as it sort of overwrites the old one.
It also then still doesn't work as it thinks psutil is is not there but its clearly there even in the virtual env.

Debug Message

Other Steps to Reproduce

Just install a esp-idf via git clone and then running the install.sh script and then . ./export.sh
then launch vscode and tell the idf extension to use a existing setup.
It will then try to download the idf even though there is already one setup.

I have checked existing issues, online documentation and the Troubleshooting Guide

  • I confirm I have checked existing issues, online documentation and Troubleshooting guide.

Metadata

Metadata

Assignees

Labels

bug-reportBug Report from users on Github (don't use this tag manually, its supposed to be used via the issue)staleStale PR or Issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions