New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connect enoent error #4332
Comments
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? |
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. |
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. |
Prerequisites
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
The text was updated successfully, but these errors were encountered: