Select Python Interpreter could not recognize the Miniconda enviroments

[guotuofeng]

Environment data

• VS Code version: 1.56.2
• Extension version (available under the Extensions sidebar): v2021.5.842923320
• OS and version: Windows 10 Enterprise (21H1) (19043.985)
• Python version (& distribution if applicable, e.g. Anaconda): Miniconda3-Python 3.7.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Relevant/affected Python packages and their versions: XXX
• Relevant/affected Python-related VS Code extensions and their versions: XXX
• Value of the python.languageServer setting: Pylance

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

When run "Python: Select Interpreter", all installed Miniconda environment should be discovered.

Actual behaviour

The dropdown list can only show part of the Miniconda environments in my machine.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

The select interpreter is broken in my machine, which seems be related to %USERPROFILE%\AppData\Roaming\Code\User\globalStorage\state.vscdb

The select interpreter can only show the python associated with current project. If I delete the state.vscdb cache file, the select interpreter could discovered all available Miniconda environments. On the other hand, if I restore state.vscdb, the issue will happen again like the screenshot shown.

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

[guotuofeng]

add the vscode database.
state.zip

[kimadeline]

Hi @guotuofeng, thank you for reaching out!

What happens if you use the "Clear Internal Extension Cache" command?

[guotuofeng]

Hi @guotuofeng, thank you for reaching out!

What happens if you use the "Clear Internal Extension Cache" command?

I tried out but it doesn't help. The issue is still there.

[CatNofishing]

Similiar issue

[wjx0912]

Similiar issue too.

[kimadeline]

@CatNofishing and @wjx0912, what do you mean by similar issue? If you delete the state.vscdb cache file, the select interpreter command can discover all available Miniconda environments?

[guotuofeng]

Might be related with this issue: microsoft/vscode-jupyter#10552, since I hit the case as well.

[kimadeline]

Hi everyone, is this issue still happening?

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.