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

Handle errors from Dynamic Debug Configuration providers #202622

Merged
merged 5 commits into from
Jul 29, 2024

Conversation

walter-erquinigo
Copy link
Contributor

@walter-erquinigo walter-erquinigo commented Jan 16, 2024

If a Dynamic Configuration provider, via its method provideDebugConfigurations, returns undefined or throws an Error, the selector in the Debug Tab is left in a borked state instead of going back to the last selected item. This was initially reported in #198798, whose fix handled some cases, but not all. This commit attempts to handle all the remaining cases.

The easiest way to test this, is to use a provider and return an Error from provideDebugConfigurations or return undefined and make sure that the Debug Tab selector is left unchanged.

Related issue: #202623

If a Dynamic Configuration provider, via its method `provideDebugConfigurations`, returns `undefined` or throws an Error, the selector in the Debug Tab is left in a borked state instead of going back to the last selected item. 
This was initially reported in microsoft#198798, whose fix handled some cases, but not all. This commit attempts to handle all the remaining cases.
@roblourens roblourens modified the milestones: May 2024, June 2024 May 29, 2024
@roblourens roblourens modified the milestones: June 2024, July 2024 Jun 25, 2024
@roblourens roblourens modified the milestones: July 2024, August 2024 Jul 24, 2024
roblourens
roblourens previously approved these changes Jul 27, 2024
Copy link
Member

@roblourens roblourens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry it took so long to get to this. Thanks for the PR!

@roblourens
Copy link
Member

And you'll need to reply to the CLA bot. Not sure why it didn't show up before.

kieferrm
kieferrm previously approved these changes Jul 27, 2024
@walter-erquinigo
Copy link
Contributor Author

@microsoft-github-policy-service agree company="Modular, Inc"

@walter-erquinigo
Copy link
Contributor Author

@walter-erquinigo please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Modular, Inc"

@walter-erquinigo
Copy link
Contributor Author

@roblourens , thank you!!

@walter-erquinigo
Copy link
Contributor Author

Thank you guys for the review!!! Happy to contribute with more debugging stuff.

@walter-erquinigo
Copy link
Contributor Author

@roblourens , do you need to me to the rebase or will you manage that on your own?

@roblourens roblourens dismissed stale reviews from kieferrm and themself via dcf79fb July 29, 2024 16:12
@roblourens
Copy link
Member

I'll take it from here, thanks

@roblourens roblourens merged commit e3b1073 into microsoft:main Jul 29, 2024
6 checks passed
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Sep 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants