microsoft / microsoft/vscode-remote-release

`Remote SSH: Kill current VS Code server` doesn't work

Open
#10,114 4 comments 4 reactions 1 assignee View on GitHub

@roblourens is already working on this.

Since Jul 30, 2024.

bug ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Command Remote SSH: Kill current VS Code server doesn't work using the most updated code server. As it is expected to be installed in the folder .vscode-server\cli instead of .vscode-server\bin. So it raise error message and log like

Get-Process node | Where-Object Path -match ".*\\.vscode-server.*\\bin\\.*" | ForEach-Object {Stop-Process -Id $_.Id}
> PS C:\Users\xxxx> Remove-Item -Force -Recurse $env:USERPROFILE\.vscode-server\bin
> +             Remove-Item -Force -Recurse $env:USERPROFILE\.vscode-serv ...
> +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>     + CategoryInfo          : ObjectNotFound: (C:\Users\xxx\.vscode-server\bin:String) [Remove-Item], ItemNotFoun 
>    dException
>     + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand
  • VSCode Version: 1.91.1
  • Local OS Version: Windows 11
  • Remote OS Version: Windows 2019
  • Remote Extension/Connection Type: Server (SSH)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.