Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Extension appends malformed string to PATH

Aberta
  • Algo errado?
#1,666 1 comentário 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@wenytang-ms já está trabalhando nisso.

Desde 10/8/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

ai-triaged bug

Having this extension installed breaks Git Graph.
Someone else has also reported this on the ratings page on Visual Studio Markteplace

The Git Graph shell outputs the following:

PS C:\Users\df\repos\simonegit> git rebase --interactive 5aa86aa181b6e698563d26909279fe2b7d4a7d75
git: Cannot find drive. A drive with the name '.c' does not exist.

The vscode-java-debug extension is appending
".c:\Users\df.vscode\extensions\vscjava.vscode-java-debug-0.59.0\bundled\scripts\noConfigScripts"
to the PATH of the powershell.

Hovering over the Tab in The Vscode Terminal Pane shows:

Process ID (PID): 92924

Command line: …\pwsh.exe -noexit -command 'try { . "c:\Users\df\AppData\Local\Programs\Microsoft VS Code\df53daabb1\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1" } catch {}'

Shell integration: Rich

 The following extensions want to relaunch the terminal to contribute to its environment:

vscjava.vscode-java-debug

The full terminal output for context:

PS C:\Users\df\repos\simonegit> git rebase --interactive 5aa86aa181b6e698563d26909279fe2b7d4a7d75
git: Cannot find drive. A drive with the name '.c' does not exist.
PS C:\Users\df\repos\simonegit> [System.Environment]::GetEnvironmentVariable("Path") -split ';'
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.6.4.0_x64__8wekyb3d8bbwe
c:\Users\df\.vscode\extensions\vadimcn.vscode-lldb-1.12.2\bin
c:\Users\df\AppData\Roaming\Code\User\globalStorage\github.copilot-chat\debugCommand
c:\Users\df\AppData\Roaming\Code\User\globalStorage\github.copilot-chat\copilotCli
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v13.3\bin\x64
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v13.3\bin
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Program Files\dotnet\
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
C:\Program Files\WireGuard\
C:\Program Files\PuTTY\
C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
C:\Program Files\Docker\Docker\resources\bin
C:\Program Files\usbipd-win\
C:\Program Files\LLVM\bin
C:\Program Files\Graphviz\bin
C:\Program Files\Git\cmd
C:\Program Files\nodejs\
C:\Strawberry\perl\site\bin
C:\Strawberry\perl\bin
C:\Program Files\NVIDIA Corporation\Nsight Compute 2026.2.0\
C:\Program Files\CMake\bin
C:\Users\df\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\Scripts\
C:\Users\df\AppData\Local\Programs\Python\Python312\Scripts\
C:\Users\df\AppData\Local\Programs\Python\Python312\
C:\Users\df\AppData\Local\Programs\Python\Launcher\
C:\Users\df\AppData\Local\Microsoft\WindowsApps
C:\Users\df\AppData\Local\Programs\Microsoft VS Code\bin
C:\Users\df\AppData\Local\Microsoft\WinGet\Packages\Ninja-build.Ninja_Microsoft.Winget.Source_8wekyb3d8bbwe
C:\Users\df\AppData\Local\Microsoft\WinGet\Packages\Docker.DockerCompose_Microsoft.Winget.Source_8wekyb3d8bbwe
C:\Users\df\AppData\Local\Microsoft\WinGet\Packages\astral-sh.uv_Microsoft.Winget.Source_8wekyb3d8bbwe
C:\Users\df\.dotnet\tools
C:\Users\df\AppData\Roaming\npm
C:\Users\df\AppData\Local\Programs\MiKTeX\miktex\bin\x64\
C:\Users\df\.lmstudio\bin
C:\Users\df\AppData\Local\Microsoft\WinGet\Packages\ggml.llamacpp_Microsoft.Winget.Source_8wekyb3d8bbwe
C:\Users\df\AppData\Local\PowerToys\DSCModules\
C:\Users\df\AppData\Local\Microsoft\WinGet\Links
.c:\Users\df\.vscode\extensions\vscjava.vscode-java-debug-0.59.0\bundled\scripts\noConfigScripts
Linguagem predominante
TypeScript
Estrelas
591
Forks
429
Merge médio
1d 1h
PRs com merge (30d)
20

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-java-debug

Todas as issues de microsoft/vscode-java-debug

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.