search

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.61k stars 275 forks source link

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

Open VSCodeTriageBot opened 2 years ago

VSCodeTriageBot commented 2 years ago 
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 commented 2 years ago

@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.

dokutoshi commented 3 months ago

Any updates on this error. @eleanorjboyd The error appears in VS Code 1.90 using Remote SSH. image

roblourens commented 3 months ago

You should be able to ignore it

dokutoshi commented 1 month ago

i believe it is related to a related issue kernels reset for dynamic folders @roblourens

You should be able to ignore it