Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

attempting to enter debugger from commandline gives error in extension version 2025.0.0

Abierto
  • ¿Algo no está bien?
#5,175 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
powershell, typescript, vscode
Área
developer-experience, devtools

Línea de trabajo

Reproduce el fallo en el terminal de PowerShell con wait-debugger o Get-Process -Name bogus -ErrorAction Break usando la versión 2025.0.0 de la extensión y VS Code 1.98.1. Empieza localizando la ruta de logging actual de la extensión y comparando el comportamiento con una versión anterior de la extensión; se considera terminado cuando la depuración activada desde el terminal se abre de forma fiable sin el error del editor y se identifican los logs relevantes o una causa de la regresión.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Area-Debugging Issue-Bug Verified
Prerequisites
  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.
Summary

Starting with Powershell extension version 2025.0.0, whenever I do something at the terminal command prompt that tries to engage the debugger, a screen opens up with this error message, "The editor could not be opened due to an unexpected error. Please consult the log for more details."

Image

I found logs at ...AppData\Roaming\Code\User\globalStorage\ms-vscode.powershell\logs , but the files under the random GUID type folder there haven't been written to since February; so, I don't know what that means or if there are logs elsewhere.

Usually, I can open another file, paste my command in there and hit F5 and that works. But, sometimes even then I get the error message. And, that's pretty clumsy. In previous versions of the extension, I was able to put wait-debugger; in front of my command when I wanted to make it go into the debugger. But, if I just run a command like Get-Process -Name bogus -ErrorAction Break I also get the error.

This has happened with 3 different machines and it's pretty consistent.

Does anyone use something other than VS Code with the Powershell extension to debug Powershell scripts? What's the most popular way to do this?

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.4.7
PSEdition                      Core
GitCommitId                    7.4.7
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Name             : Visual Studio Code Host
Version          : 2025.0.0
InstanceId       : 61447b12-1895-4529-80b3-43f5430cb6fd
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-US
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
1.98.1
2fc07b811f760549dab9be9d2bedd06c51dfcb9a
x64
Extension Version
ms-vscode.?[7mpowershell?[[email protected]
Steps to Reproduce

run a command in the terminal that tries to open the debugger

Visuals

No response

Logs

No response

Lenguaje dominante
TypeScript
Estrellas
1.9k
Forks
549
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PowerShell/vscode-powershell

Todos los issues de PowerShell/vscode-powershell

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.