Skip to content
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

Getting started page awaits a lifecycle phase in setInput? #183249

Closed
bpasero opened this issue May 23, 2023 · 2 comments · Fixed by #183273
Closed

Getting started page awaits a lifecycle phase in setInput? #183249

bpasero opened this issue May 23, 2023 · 2 comments · Fixed by #183273
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented May 23, 2023

(found this because this actually resulted in a error: #183226)

Code is here:

await this.lifecycleService.when(LifecyclePhase.Restored);

I do not fully understand this, but instead of awaiting the phase in setInput, why not await it before opening the welcome page? And why does not wait at all there, what is the reason?

I think this may also be the cause of #181660

@bhavyaus
Copy link
Contributor

My bad. I wasn't aware that the ContextKeyHandler was also using the EditorInput to performs checks.
My main goal with introducing that check in #182947 was to check for all service ready before I attempted to fetch content for the welcome page.

I think this may also be the cause of #181660

This was a change I introduced last Friday and #181660 precedes it. I've already fixed the issue with: #182796

@bpasero
Copy link
Member Author

bpasero commented May 24, 2023

My main goal was to check for all service ready before I attempted to fetch content for the welcome page.

Can you clarify what "all services ready" means for example?

@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label May 24, 2023
@VSCodeTriageBot VSCodeTriageBot added this to the May 2023 milestone May 24, 2023
@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels May 25, 2023
@bhavyaus bhavyaus added the bug Issue identified by VS Code Team member as probable bug label May 31, 2023
@Tyriar Tyriar added the verified Verification succeeded label Jun 1, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jul 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants