Incorrect execution status for last command run with the PowerShell Extension
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- powershell, typescript
- 领域
- devtools
调研方向
首先,在 PowerShell 扩展的 VS Code 终端中复现报告的 FakeCommand 和 $? 序列,然后将其与 Windows Terminal 中的 PowerShell 进行比较。完成的标准是:扩展在无法识别的命令之后报告 $? 为 False,且与独立运行的 PowerShell 一致。
由索引模型根据 Issue 内容生成。
描述
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
The execution status for the last command is being incorrectly reported in the $? automatic variable when using the PowerShell Extension. While using PowerShell in Visual Studio code, the execution status is reported properly by $?.
As an aside, getting the ExecutionStatus via Get-History | Select Id,ExecutionStatus,CommandLine seems to always report 'Completed' even after encountering a "command not recognized" type of error.
Tagging @SeeminglyScience per his request via the PowerShell community Discord.
PowerShell Version
$PSVersionTable; $Host
Name Value
---- -----
PSVersion 7.5.0
PSEdition Core
GitCommitId 7.5.0
OS Microsoft Windows 10.0.26100
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 : 8ba0c99d-557c-43db-b23b-699ec7517872
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
code --version
1.98.2
ddc367ed5c8936efe395cffeec279b04ffd7db78
x64
Extension Version
code --list-extensions --show-versions | Select-String powershell
ms-vscode.powershell@2025.0.0
tylerleonhardt.vscode-inline-values-powershell@0.0.7
Steps to Reproduce
Open the VS Code terminal with the PowerShell extension. Run:
FakeCommand
$?
Then switch to PowerShell in the VS Code terminal or in Windows Terminal and run the same command.
In the PowerShell extension, it returns True.
In PowerShell, it returns False.
Visuals
Logs
No response
- 主要语言
- TypeScript
- 星标
- 1.9k
- 派生
- 548
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
PowerShell/vscode-powershell 的其他 Issue
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 62/100
PowerShell/vscode-powershell#5599 · 3 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
PowerShell/vscode-powershell#5592 · 2 条评论 · 1 个 reaction ·
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 62/100
PowerShell/vscode-powershell#5583 · 1 条评论 ·
-
powershell.scriptAnalysis.settingsPath (Description): Warning Message Should Provide A Workaround 未关闭Area-Code Formatting Issue-Enhancement
难度 1/5 1 小时以内 新手友好度 68/100
PowerShell/vscode-powershell#4653 · 3 条评论 · 4 个 reaction ·
-
agentic-workflows
难度 3/5 1-2 天 新手友好度 48/100
PowerShell/vscode-powershell#5606 ·
查看 PowerShell/vscode-powershell 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 1/5 1 小时以内 新手友好度 90/100
TanStack/tanstack.com#1293 ·