vscode-powershell: VSCODE- Insiders: Timed out waiting for the PowerShell extension to start
System Details
- Operating system name and version: Windows 10
- VS Code version: 1.18.0 Insiders (commit date 2017-10-06T05:26:16.770Z)
- PowerShell extension version: 1.4.3
- Output from
$PSVersionTable: 5.1.15063.632
Issue Description
Error: Timed out waiting for the PowerShell extension to start.
This seems to be specific for latest 1.18 insiders build. All works normally on 1.17 public version.
I tried multiple computers and its the same behaviour.
PowerShell extension is timing out when pressing F5, or trying to start any script.
Steps to reproduce
- On clean Windows 10 machine install VS Code Insiders 1.18.0.
- Install PowerShell extension v.1.4.3
- Wirite simple script (something as Write-Host 1)
- Press F5
Expected behaviour is to diplay 1 in console. But, nothing actually happens. After some time, time out error will appear.
Attached Logs
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 4
- Comments: 21
Commits related to this issue
- Update to use DebugConfigurationProvider Fix #1046 Fix warning in status bar about ThemeColor This fix requires PSES PR 556 to eliminate one PSES cause of the debug adapter to crash. Also npm gener... — committed to PowerShell/vscode-powershell by rkeithhill 7 years ago
- Update to use DebugConfigurationProvider Fix #1046 Fix warning in status bar about ThemeColor This fix requires PSES PR 556 to eliminate one PSES cause of the debug adapter to crash. Also npm gener... — committed to PowerShell/vscode-powershell by rkeithhill 7 years ago
I plan to look into this tonight.
BTW there is still an issue with “Attach to process” debugging. Separate issue that has me scratching my head. Might need @daviwil help on that one.
PR for the fix has been submitted - pending review.
Been looking at this for several hours. In the past, debug protocol changes have been minimal and simple to implement. However, the required changes for this change are bit more extensive than I was hoping they would be. It’s going to take a little while. I’m hopeful we’ll get this implemented before VSCode 1.18 drops.