-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Creating a new Conda Env creates a ton of calls to onDidChangeEnvironments #19900
Comments
This seems expected as currently we trigger a full refresh if a new environment is detected, I think that's why so many changed events were emitted. But I don't see |
Sorry the formatting was all wonky on that log. I just tried it again with a new env and I do see the new env (endgameEnv5) getting an add and an update.
Note: This is in with all the others. Still seems a bit wonky to me that I get all the other updates, just from an API expectation it's not what I was thinking, but I guess the consumers can manage things themselves if they are storing the results and just comparing on what came before. There also seem to be some entries like this that get added and removed right after so they don't ever show up in .all. Not sure what these are.
|
When running a python binary fails, they're removed from the list. Python debug logs should contain the error in detail as to why they were invalid. |
About the API itself, I'll see if there's some way that we can only fire an update for the changed environment. I see two approaches:
|
Closes #19900 Trigger a scoped refresh instead of a full refresh when an environment gets created, preferably only looking for the environment which gets created.
…thon#19922) Closes microsoft/vscode-python#19900 Trigger a scoped refresh instead of a full refresh when an environment gets created, preferably only looking for the environment which gets created.
Testing #19886
The API around onDidChangeEnvironments didn't seem to do what I was expecting when I created a new conda env. I got a ton of calls to this function, an add and an update for the new env were some where in the list, but I was just expecting an add and maybe an update for the new env. Instead it seems like I got an update for basically everything in my python list.
Repro:
conda create --name endgameEnv4 python=3.9
Debug Logging
Maybe this is expected? But It was not what I was expecting out of this event.
The text was updated successfully, but these errors were encountered: