global envs list incorrect (gets in bad state)

[eleanorjboyd]

putting this down as bug because I've run into it twice at this point, I am not exactly sure where the error is occurring but wanted to track the bug and collect information on it.

Somehow the list of global envs gets messed up (I think what happens if global envs that don't exist or maybe aren't global are added to the list) here https://github.com/eleanorjboyd/vscode-python-environments/blob/9080a9ba82cff4e5ba29cc6e1b71b0dc865f7844/src/managers/builtin/venvUtils.ts#L478-L479

const sortedEnvs = ensureGlobalEnv(basePythons, log); so the entries in the screenshot that don't have (homebrew) are not valid

[karthiknadig]

@eleanorjboyd I think this happened when you deleted .venv created with these versions right?

[eleanorjboyd]

got it again, steps:

1. load a workspace with a few packages that have their own environment
2. go to create environment, select existing package, then you see this list

[eleanorjboyd]

To verify (must have python envs extension installed, not installed by default)

• load a workspace with a few packages that have their own environment (try with this test repo: https://github.com/eleanorjboyd/python-envs-scenarios)
• go to create environment (command palette), click select existing package, then you see this list of versions to choose from
• verify no duplicates exist in the list

[amunger]

@eleanorjboyd - do I need to open the WS in some special way to get "select existing package" as an option?

[eleanorjboyd]

ok sorry I got the steps wrong, you just need to go where you are in the screenshot then select venv and a list will show with the environments you can choose from