Skip to content

Creating two conda environments and then running makes only one show up #18751

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

Closed
rchiodo opened this issue Mar 22, 2022 · 11 comments
Closed

Creating two conda environments and then running makes only one show up #18751

rchiodo opened this issue Mar 22, 2022 · 11 comments
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@rchiodo
Copy link

rchiodo commented Mar 22, 2022

Testing #18731

Did this:

conda create -n testNoPython1
conda create -n testNoPython2

Then created a python file
Then ran the python file
Python file ran
Then selected an interpreter to try to pick 'testNoPython2'.

It wasn't listed.

I hit refresh and this happens:

image

Every time I hit refresh another instance(s) of testNoPython1 appears.

@rchiodo
Copy link
Author

rchiodo commented Mar 22, 2022

Without the filter I now have this in my list:

image

@rchiodo
Copy link
Author

rchiodo commented Mar 22, 2022

Might be a dupe of #18749

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Mar 22, 2022
@karrtikr
Copy link

I see, so everything is fine until a second environment is created using

conda create -n testNoPython2

?

@rchiodo
Copy link
Author

rchiodo commented Mar 22, 2022

No I created both of them ahead of time. Everything is fine until I ran something with python.

@karrtikr
Copy link

karrtikr commented Mar 23, 2022

Then ran the python file

I assume you ran it using the play button and using testNoPython1 as interpreter? I'm not sure how running could influence discovery.

Also, what do you see when you close the list and open it again, is testNoPython1 still duplicated?

I plan to work on #18749 with Karthik first (can't repro that either) and may ask verbose logs later if that doesn't fix this issue.

@rchiodo
Copy link
Author

rchiodo commented Mar 23, 2022

Yeah reloading the window still showed multiple copies.

@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug triage area-environments Features relating to handling interpreter environments and removed triage-needed Needs assignment to the proper sub-team labels Mar 23, 2022
@rchiodo
Copy link
Author

rchiodo commented Mar 23, 2022

After the latest build, I get this now.

  • Initial interpreter list only includes one of my environments:
    image

  • Forcing a refresh lists the other one
    image

@karrtikr
Copy link

Initial interpreter list only includes one of my environments:

I see, did you wait for the initial refresh to finish? (Did "Discovering Python Interpreters" text disappear?)

I assume you created new envs before the extension was started. If so, I would again require the verbose logs until the initial interpreter list is loaded.

Thanks for helping with this.

@karrtikr karrtikr added info-needed Issue requires more information from poster investigating We are looking into the cause of the issue and removed triage labels Mar 23, 2022
@rchiodo
Copy link
Author

rchiodo commented Mar 23, 2022

I assume it was up to date. No more output was coming in the python output tab. I get this:

image

Here's the log:
pythonlog.txt

@karrtikr karrtikr removed the info-needed Issue requires more information from poster label Mar 23, 2022
@karrtikr
Copy link

Please try the latest build: https://github.com/microsoft/vscode-python/suites/5784118548/artifacts/192898285, where we now use conda.bat over conda.exe.

@karrtikr karrtikr added info-needed Issue requires more information from poster needs PR verified Verification succeeded and removed info-needed Issue requires more information from poster investigating We are looking into the cause of the issue labels Mar 24, 2022
@karrtikr
Copy link

Verified offline that it works with the latest bits.

@karrtikr karrtikr added this to the March 2022 milestone Mar 24, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants