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.

Sign up for GitHub

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

Jump to bottom

Unable to enable extension that depends on another disabled extension (AzML) #144294

Closed
greazer opened this issue Mar 3, 2022 · 7 comments
Closed

Unable to enable extension that depends on another disabled extension (AzML) #144294

greazer opened this issue Mar 3, 2022 · 7 comments
Assignees
@sandy081
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone
April 2022

Comments

@greazer
Copy link
Member

greazer commented Mar 3, 2022

The Azure ML extension requires itself and the Azure ML Remote extension to b enabled in order to operate. It seems that the situation is detected, but when VS Code prompts to enable the main extension it fails silently and asks again and again.
EnableBug
@sandy081 sandy081 added the bug Issue identified by VS Code Team member as probable bug label Mar 7, 2022
@sandy081 sandy081 added this to the Backlog milestone Mar 7, 2022
@joaomoreno joaomoreno modified the milestones: Backlog, April 2022 Mar 31, 2022
@kieferrm kieferrm mentioned this issue Apr 3, 2022
Closed
@sandy081 sandy081 added the extensions Issues concerning extensions label Apr 4, 2022
@sandy081 sandy081 added the author-verification-requested Issues potentially verifiable by issue author label Apr 4, 2022
@kieferrm kieferrm mentioned this issue Apr 26, 2022
Closed
15 tasks
@connor4312
Copy link
Member

@greazer could you verify this issue or share steps on how to get into that scenario with the AML extension?

@connor4312 connor4312 added the verification-steps-needed Steps to verify are needed for verification label Apr 28, 2022
@sandy081
Copy link
Member

Verification steps:

  • Install sandy081.999-urlhanlder extension
  • Disable sandy081.999-urlhanlder and sandy081.998-test-code extensions
  • Open following url code --open-url vscode://sandy081.999-urlhanlder/helloWorld
  • Make sure you are asked to Enable the extension and Open the URL
  • Clicking on Enable and Open shall enable above two extensions and show /helloWorld notification

@sandy081 sandy081 removed the verification-steps-needed Steps to verify are needed for verification label Apr 28, 2022
@connor4312
Copy link
Member

Thanks! Will verify after lunch if no one gets to it faster

@connor4312 connor4312 added the verified Verification succeeded label Apr 28, 2022
@ChaseKnowlden
Copy link
Contributor

Doesn't show Hello World Notification and Doesn't enable both extensions.

@ChaseKnowlden
Copy link
Contributor

Doesn't show Hello World Notification and Doesn't enable both extensions on Stable, but verification steps work on insiders.

@sandy081
Copy link
Member

Fix is in insiders only. Stable will be released next week.

@github-actions github-actions bot locked and limited conversation to collaborators May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sandy081 sandy081

Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Milestone
April 2022
Development

No branches or pull requests
6 participants
@joaomoreno @connor4312 @sandy081 @greazer @ChaseKnowlden and others