Path to script inserted into console on F5

[PrzemyslawKlys]

Prerequisites

• I have written a descriptive issue title.
• I have searched all 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

Whenever I run PowerShell script I get the path to the script in the console

You can see this in GIF

It's a bit of random.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22000.653
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.653
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
x64

Extension Version

ms-vscode.powershell@2022.6.1                                                                                     
ms-vscode.powershell-preview@2022.6.2                                                                             
tobysmith568.run-in-powershell@1.1.1                                                                              
TylerLeonhardt.vscode-inline-values-powershell@0.0.6

Steps to Reproduce

Run script with F5

Visuals

No response

Logs

No response

[fflaten]

Also occurs using Pester code lense.
It mostly/only occurs after you've executed something in the terminal. Ex. F5, ctrl+c to remove the invoked command, then f5 -> nothing. "dir" + enter, then F5 -> command is left in console.

[andyleejordan]

The first entry is as-designed. F5 means "run script" and so runs exactly the command as printed. The extra one you're seeing afterwards was just fixed in PowerShell/PowerShellEditorServices#1841, and was another way #4041 showed up.

[ghost]

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.