-
Notifications
You must be signed in to change notification settings - Fork 325
Explore not resolving an environment using Python API unless selected #15140
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
Comments
This was referenced Feb 28, 2024
Based on the VSIX provided to slack, it still seems to call
|
Feel free to close this if this is no longer the issue, reopening currently based on what I observed in the logs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Currently it looks like Jupyter is resolving all environments discovered in the system leading to execution for those binaries, which could be avoided. Just as it is in the Python extension.
Related: #12719
Practically speaking,
known
should serve as a good enough alternative for display purposes. It might have partial (best-effort) data at first, but is corrected/populated with full information soon anyways, once discovery finishes.The text was updated successfully, but these errors were encountered: