Skip to content

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

Merged
merged 6 commits into from
Apr 30, 2021

Conversation

karrtikr
Copy link

@karrtikr karrtikr commented Apr 15, 2021

@karrtikr karrtikr added the no-changelog No news entry required label Apr 15, 2021
@karrtikr karrtikr force-pushed the fs branch 2 times, most recently from 87d2ecc to 4663fa3 Compare April 15, 2021 21:02
@karrtikr karrtikr changed the title Ensure extension is ready for use faster Block on getting selected interpreter in the status bar on startup Apr 26, 2021
@karrtikr karrtikr changed the title Block on getting selected interpreter in the status bar on startup Block on displaying selected interpreter in the status bar on startup Apr 26, 2021
@karrtikr karrtikr marked this pull request as ready for review April 28, 2021 21:17
@karthiknadig
Copy link
Member

@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

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?

Copy link
Author

@karrtikr karrtikr Apr 29, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog No news entry required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants