Error on Debug Adapter: Error: connect ETIMEDOUT \\.\pipe\... after second execution in PowerShell Integrated Terminal

[hugh-martin]

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 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

Code screenshots.zip

Logs

logs.zip

[hugh-martin]

I disabled the PowerShell extension, installed the PowerShell Preview extension (ms-vscode.powershell-preview@2021.8.0) and got the same results.

[andyleejordan]

@hugh-martin and @youngr137, could this be a duplicate of #2821?

[hugh-martin]

@andschwa, I do not believe so. I don't see any errors or timeouts in vscode-powershell.log from #2821. Also, in my case, I avoided using debug at all, which seems to be the focus of that issue.

[hugh-martin]

FYI, I cannot duplicate the issue with PowerShell extension v2021.6.2. Switching back to v2021.8.0 of the PowerShell extension brings the issue back.

[andyleejordan]

Oh that's interesting! Ok, can you let me know if it reproduces with v2021.7.0-preview? This would help me narrow it down!

[hugh-martin]

I just tried it and I cannot reproduce it with v2021.7.0-preview.

[andyleejordan]

Fantastic, thanks!

[andyleejordan]

So that narrows down the bug to be either a change between PowerShell Editor Services v2.4.6 and v2.4.7, as there isn't a substantial code change to the extension that I can see between v2021.7.0-preview and v2021.8.0.

[andyleejordan]

@rjmholt, @dkattan, any ideas? I'll try to repro locally.

[hugh-martin]

For whatever it's worth, I have been working with PowerShell extension v2021.6.2 for several days now and the problem has not re-occurred. Thanks again for the efforts.

[andyleejordan]

Just FYI this is on my docket to investigate as the next big problem happening.

[andyleejordan]

I've been attempting to look at this and have not been able to reproduce it yet. PowerShell Preview 2021.8.2 is out now, would you test and see if this still reproduces?

[hugh-martin]

I am happy to report that it is not happening with PowerShell Preview 2021.8.2 and PowerShell 7.1.3.

[andyleejordan]

Woo-hoo!

[ghost]

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