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

Opening a new window shows a prompt that GitHub extension cannot be activated #125395

Closed
sandy081 opened this issue Jun 3, 2021 · 5 comments
Closed
Assignees
Labels
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

Comments

@sandy081
Copy link
Member

sandy081 commented Jun 3, 2021

Steps to Reproduce:

  1. Open a new window. Following prompt is shown

image

@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions labels Jun 3, 2021
@sandy081 sandy081 added this to the May 2021 milestone Jun 3, 2021
@sandy081 sandy081 self-assigned this Jun 3, 2021
@sandy081
Copy link
Member Author

sandy081 commented Jun 3, 2021

This is because Git extension is disabled because of workspace trust and GitHub extension is enabled (as it supported). Actual fix is to disable GitHub extension which will be taken care here - #122448.

Did a pragmatic fix here:

  • Fixed the prompt in this case by providing appropriate message and no actions are shown.

image

  • In order to provide better experience OOB ie., not to show these error prompts, made GitHub extension to not to support untrusted workspaces as its dependency Git extensions does not. It means that above prompt is not shown OOB.

@lszomoru
Copy link
Member

lszomoru commented Jun 3, 2021

@sandy081, in case that we detect that the dependency is not loaded due to workspace trust, could we be more specific in the message - Cannot activate the X extension because it depends on the Y extensions which is not supported in Restricted Mode. Could we also add an action called Manage Workspace Trust which would open the workspace trust editor?

@sandy081
Copy link
Member Author

sandy081 commented Jun 3, 2021

Done

@chrmarti
Copy link
Contributor

chrmarti commented Jun 3, 2021

Cloning a Repository Container now fails in a new empty window (and untrusted workspaces in general): microsoft/vscode-remote-release#5134. Is there a way to make the repository picker available when the workspace is not trusted yet?

eamodio pushed a commit that referenced this issue Jun 3, 2021
Re-enables GitHub extension in untrusted workspaces

From commit 01c6fb5
@sandy081
Copy link
Member Author

sandy081 commented Jun 4, 2021

It seems @eamodio changed back to support git & GitHub extensions to be supported in untrusted workspaces. So @chrmarti your scenario shall work now.

@rzhao271 rzhao271 added the verified Verification succeeded label Jun 4, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 18, 2021
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 extensions Issues concerning extensions insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants
@lszomoru @rzhao271 @chrmarti @sandy081 and others