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 'remote-internal.setActiveFolders' not found #7178

Open
VSCodeTriageBot opened this issue Sep 9, 2022 · 1 comment
Open

command 'remote-internal.setActiveFolders' not found #7178

VSCodeTriageBot opened this issue Sep 9, 2022 · 1 comment
Assignees

Comments

@VSCodeTriageBot
Copy link
Collaborator

Error: command 'remote-internal.setActiveFolders' not found
at v._tryExecuteCommand in src/vs/workbench/services/commands/common/commandService.ts:91:26
at v.executeCommand in src/vs/workbench/services/commands/common/commandService.ts:85:15
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)

Go to Errors Site

@roblourens roblourens transferred this issue from microsoft/vscode Sep 9, 2022
@roblourens
Copy link
Member

@eleanorjboyd this is an error that was reported to vscode's error telemetry. I see that remote-ssh will call this command on the remote-explorer extension whether or not that extension is installed, so we should at least be checking that.

Also I'm not entirely sure why this command exists - I see remote-ssh has a "get" command which looks similar, and it seems like ideally remote-ssh would only expose "getXYZ" commands for the explorer to call whenever it needs data, instead of calling a "set" command on the explorer which forces it to activate, maybe unnecessarily.

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

No branches or pull requests

3 participants