PowerShell / PowerShell/vscode-powershell

Bug/Regression? Debugger terminal commands require Enter in attached process console

未关闭
#5,347 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

Issue-Bug Needs: Triage
主要语言
TypeScript
星标
1.9k
派生
548
PR 合并指标
30 天内没有已合并 PR

描述

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

Debugger terminal commands require Enter in attached process console.

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26200
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.5.0
InstanceId       : d51c83ef-d689-470d-914b-04cfe94b45b9
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
1.106.3
bf9252a2fb45be6893dd8870c0bf37e2e1766d61
x64
Extension Version
ms-vscode.powershell@2025.5.0
Steps to Reproduce

(1) Open pwsh console (or in my case an app hosting PowerShell Core).

(2) In VSCode, attach to this process for PowerShell debugging.

(3) In pwsh, invoke the attached script debug-4489.far.ps1 -- it sets some breakpoints for testing.
debug-4489.far.ps1.zip

(4) In pwsh, type and invoke test1 -- it breaks into VSCode debugger.

(5) In VSCode terminal type $host and hit Enter.

Expected result
VSCode evaluates the statement $host and prints the output (the host properties in this result).
It definitely used to work like this some versions ago.

Actual result
Nothing happens in the terminal until we go to the attached pwsh console and hit Enter there.
(Why? And how a user is supposed to know this?)

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

使用 debug-4489.far.ps1 进行复现:将 VS Code 附加到 pwsh,调用 test1,并在 VS Code 终端中输入 $host。跟踪附加进程的控制台和终端输入流程;当 $host 完成求值并打印主机属性,且无需在附加的 pwsh 控制台中按 Enter 时,即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
powershell, typescript, vscode
领域
devtools
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。