connect enoent error

[Mlsoun]

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

restart pwsh konsole (click on Trash icon). After this press F5 for Debug. Error message "connect enoent \.\pipe\pses_jvpn4k2y.dfi"

PowerShell Version

7.3.1

Visual Studio Code Version

1.74.1

Extension Version

Powershell v2022.11.0

Steps to Reproduce

restart pwsh konsole (click on Trash icon). After this press F5 for Debug. Error message "connect enoent \.\pipe\pses_jvpn4k2y.dfi"

Visuals

Logs

No response

[andyleejordan]

If you've clicked the trash icon, you've closed the PowerShell Extension Terminal, so then trying to debug isn't going to work unless you restart the terminal. Can you first ensure the extension terminal is started?

[Mlsoun]

Yes - you are absolutely right. Terminal is not running and Error occurs. This is the reason.
I have the news. Normally two notifications windows are popup and I click on Yes - it restarts the powershell extension terminal and then I can start debugging again without problem.

Now I discovered the real procedure to simulate the error -
I press F5 for debugging the code and when terminal is waiting for user input on Read-Host instruction and I click on Trash icon, the second notification windows does not appear (this is a bug I mean) and I cannot click on Yes for restarting terminal. When I press F5 for debugging, the reported Error message "connect enoent .\pipe\pses_jvpn4k2y.dfi" occurs. Now helps only close and start the VSCode

[Mlsoun]

Next progress - Close the VSCode is not needed - just press Ctrl +Shift+P , type "restart" and select "Powershell: Restart session". Than I can start debugging

[andyleejordan]

Sounds good. Just make sure you keep that Extension Terminal up if you want to use it. As that notice notes, IntelliSense and other features (such as debugging and F5 etc.) will not work without it! I would recommend just not clicking the trash icon.

[Mlsoun]

The reason why I click on the Trash icon is because IntelliSense has stopped working. Now should I find How can i reset the Intellisense :-)

This issue has been marked as answered and has not had any activity in a day. It has been automatically closed for housekeeping purposes.