-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Block on displaying selected interpreter in the status bar on startup #15971
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
Conversation
87d2ecc
to
4663fa3
Compare
@karrtikr can you rebase with main. The Sonar issue should be fixed in main. |
@@ -193,10 +198,6 @@ async function activateLegacy(ext: ExtensionState): Promise<ActivationResult> { | |||
|
|||
serviceManager.get<ICodeExecutionManager>(ICodeExecutionManager).registerCommands(); | |||
|
|||
interpreterManager |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were there any issues caused by the absence of await
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The extension would finish loading (Python extension loading...
text would disappear) but the user won't see the selected interpreter in the status bar, which might be confusing.
This improves things a bit, but it might increase extension activation time we record in telemetry.
For https://github.com/microsoft/vscode-python-internalbacklog/issues/149 closes https://github.com/microsoft/vscode-python-internalbacklog/issues/156
This means we need to make the process of getting active interpreter faster.