Error on Debug Adapter: Error: connect ETIMEDOUT \\.\pipe\... after second execution in PowerShell Integrated Terminal
See original GitHub issuePrerequisites
- 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 have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
Summary
Any second execution of PowerShell code results in an error in the PowerShell Extension logs and a failure to execute any code in the PowerShell Integrated Terminal until it is killed and restarted.
PowerShell Version
Name Value
---- -----
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visual Studio Code Version
1.59.0
379476f0e13988d90fab105c5c19e7abc8b1dea8
x64
Extension Version
ms-vscode.powershell@2021.5.1
ms-vscode.powershell@2021.8.0
Steps to Reproduce
Disable all extensions except the PowerShell extension. Create new file (no need to save it, but saving it will result in the same issue). Wait for the PowerShell Integrated Terminal to start. Add a small bit of PowerShell code; Get-Disk in this case, which was chosen arbitrarily. Run the script (with or without debugging). Wait for the script to execute successfully. Run the script (with or without debugging) a second time. Wait for the script to time out (~30 seconds). Check the PowerShell Extension logs for something similar to the following: Error on Debug Adapter: Error: connect ETIMEDOUT \.\pipe\PSES_x0wt2evy.fli
Visuals
Logs
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (9 by maintainers)
Top GitHub Comments
I am happy to report that it is not happening with PowerShell Preview 2021.8.2 and PowerShell 7.1.3.
Just FYI this is on my docket to investigate as the next big problem happening.