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

command 'vscode-docker.images.selectGroupBy' already exists #1008

Closed
tvilot opened this issue Jun 18, 2019 · 12 comments
Closed

command 'vscode-docker.images.selectGroupBy' already exists #1008

tvilot opened this issue Jun 18, 2019 · 12 comments

Comments

@tvilot
Copy link

tvilot commented Jun 18, 2019

Repro steps:

Action: docker.activate
Error type: Error
Error Message: command 'vscode-docker.images.selectGroupBy' already exists

Version: 0.6.3
OS: linux
Product: Visual Studio Code
Product Version: 1.35.1
Language: en

Call Stack
d.registerCommand extensionHostProcess.js:497:447
Object.registerCommand extensionHostProcess.js:716:422
Object.module.exports.t.registerCommand extension.bundle.js:211:110531
ue extension.bundle.js:157:609314
Object.<anonymous> extension.bundle.js:157:611927
Object.<anonymous> extension.bundle.js:1:394616
module.exports.n extension.bundle.js:1:392954
module.exports.n extension.bundle.js:1:392731
Object.module.exports.t.callWithTelemetryAndErrorHandling extension.bundle.js:1:394533
Object.module.exports.t.activateInternal extension.bundle.js:157:610822
@ejizba
Copy link
Member

ejizba commented Jun 18, 2019

@tvilot we just changed the publisher from "PeterJausovec" to "ms-azuretools". It's possible your machine still has an extension under the old publisher. Can you try reloading VS Code?

As a manual workaround, you can go to your "Extensions" page and uninstall v0.6.2 of the extension with "PeterJausovec" as the publisher:
Screen Shot 2019-06-18 at 6 01 54 PM

@ejizba ejizba pinned this issue Jun 18, 2019
@ejizba ejizba changed the title 'vscode-docker.images.selectGroupBy' already exists command 'vscode-docker.images.selectGroupBy' already exists Jun 18, 2019
@rrmistry
Copy link

rrmistry commented Jun 19, 2019

@EricJizbaMSFT , a clean uninstall -> reload VS Code -> install of ms-azuretools.vscode-docker seems to have resolved the issue. Thank you!

Edit: clean uninstall existing docker extension (not VS Code)

@IEvangelist
Copy link
Member

I'm experiencing the same issue and I have a clean install of vscode and the following extensions:

code --install-extension Acrolinx.vscode-sidebar
code --install-extension akamud.vscode-theme-onedark
code --install-extension DavidAnson.vscode-markdownlint       
code --install-extension docsmsft.docs-article-templates      
code --install-extension docsmsft.docs-authoring-pack
code --install-extension docsmsft.docs-markdown
code --install-extension docsmsft.docs-preview
code --install-extension docsmsft.docs-yaml
code --install-extension Equinusocio.vsc-material-theme       
code --install-extension ms-azuretools.vscode-docker
code --install-extension ms-vscode.azurecli
code --install-extension ms-vsliveshare.vsliveshare
code --install-extension PKief.material-icon-theme
code --install-extension redhat.vscode-yaml
code --install-extension streetsidesoftware.code-spell-checker

@IEvangelist
Copy link
Member

@tvilot we just changed the publisher from "PeterJausovec" to "ms-azuretools". It's possible your machine still has an extension under the old publisher. Can you try reloading VS Code?
As a manual workaround, you can go to your "Extensions" page and uninstall v0.6.2 of the extension with "PeterJausovec" as the publisher:

This doesn't seem to be the issue. I am experiencing it from a clean install.

@StephenWeatherford
Copy link
Contributor

StephenWeatherford commented Jun 25, 2019

@arush0 @IEvangelist @tvilot This should have been fixed with the 0.6.4 update last week. If that's not the case, could you please let us know? Thanks!

Current known status:
The most recent update is 0,.6.4 (with the new publisher name)
Vscode still recommends the 0.6.2 extension with the old publisher name (will be fixed with next vscode update - see #1075)
It should be okay to have both the old and new publisher versions installed (0.6.2 and 0.6.4), everything should still work as expected (once vscode is fixed, we'll put in a patch to recommend uninstalling the old one)

@IEvangelist
Copy link
Member

@arush0 @IEvangelist @tvilot This should have been fixed with the 0.6.4 update last week. If that's not the case, could you please let us know? Thanks!
Current known status:
The most recent update is 0,.6.4 (with the new publisher name)
Vscode still recommends the 0.6.2 extension with the old publisher name (will be fixed with next vscode update - see #1075)
It should be okay to have both the old and new publisher versions installed (0.6.2 and 0.6.4), everything should still work as expected (once vscode is fixed, we'll put in a patch to recommend uninstalling the old one)

Great, thank you @StephenWeatherford ... I have been using VS Code without experiencing the issue since I've updated - seems to have been fixed. Thanks again

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants