Skip to content

Timed out waiting for the PowerShell extension to start when Start debugging before extension starts #2358

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

Closed
gbuktenica opened this issue Dec 11, 2019 · 12 comments
Labels
Area-Debugging Issue-Bug A bug to squash. Needs: Fix Verification Please verify the fix for us! Resolution-Fixed Will close automatically.

Comments

@gbuktenica
Copy link

gbuktenica commented Dec 11, 2019

System Details

  • Operating System
    Windows 10
  • VS Code version
    1.40.2
  • PowerShell extension version
    2019.11.0
  • Output from $PSVersionTable
    7.0.0-preview.6
    5.1.18362.145

Issue Description

I am experiencing a problem with running a PowerShell debug configuration.
"PowerShell: Launch a Script"
If I do not open a ps1 file first the debugger will time out waiting for PowerShell to start.
Error: Timed out waiting for the PowerShell extension to start.

Repro Instructions

Open VSCode
Open a Folder with a launch.json and a PowerShell Script
Note: DO NOT open any POWERSHELL scripts
Open the debugger Control + Shift + D
Launch a configuration PowerShell Launch a script.

Expected Behaviour

The Launch should Run

Actual Behaviour

Error: Timed out waiting for the PowerShell extension to start.

Work around

Open a PowerShell script in the editor
Extension starts PowerShell
Run the debug configuration.
It will now work.

@ghost ghost added the Needs: Triage Maintainer attention needed! label Dec 11, 2019
@gbuktenica
Copy link
Author

gbuktenica commented Dec 11, 2019

$psEditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1       13      1       0

@gbuktenica
Copy link
Author

gbuktenica commented Dec 11, 2019

vscode-powershell.log

11/12/2019 1:26:18 pm [NORMAL] - powershell.exe terminated or terminal UI was closed

DebugAdapter.log

Session file path: c:\Users\glen\.vscode\extensions\ms-vscode.powershell-2019.11.0\sessions\PSES-VSCode-13036-Debug, pid: 2348 
Waiting for session file, tries remaining: 30...
Waiting for session file, tries remaining: 29...
Waiting for session file, tries remaining: 28...
Waiting for session file, tries remaining: 27...
Waiting for session file, tries remaining: 26...
Waiting for session file, tries remaining: 25...
Waiting for session file, tries remaining: 24...
Waiting for session file, tries remaining: 23...
Waiting for session file, tries remaining: 22...
Waiting for session file, tries remaining: 21...
Waiting for session file, tries remaining: 20...
Waiting for session file, tries remaining: 19...
Waiting for session file, tries remaining: 18...
Waiting for session file, tries remaining: 17...
Waiting for session file, tries remaining: 16...
Waiting for session file, tries remaining: 15...
Waiting for session file, tries remaining: 14...
Waiting for session file, tries remaining: 13...
Waiting for session file, tries remaining: 12...
Waiting for session file, tries remaining: 11...
Waiting for session file, tries remaining: 10...
Waiting for session file, tries remaining: 9...
Waiting for session file, tries remaining: 8...
Waiting for session file, tries remaining: 7...
Waiting for session file, tries remaining: 6...
Waiting for session file, tries remaining: 5...
Waiting for session file, tries remaining: 4...
Waiting for session file, tries remaining: 3...
Waiting for session file, tries remaining: 2...
Waiting for session file, tries remaining: 1...
Waiting for session file, tries remaining: 0...
Timed out waiting for session file!

@SydneyhSmith
Copy link
Collaborator

@gbuktenica thanks for opening this issue, we recently published an update to our Preview extension that may solve this issue, please let us know if you are able to try it out..thanks!

@SydneyhSmith SydneyhSmith added Area-Debugging Issue-Bug A bug to squash. Needs-Repro-Info and removed Needs: Triage Maintainer attention needed! labels Dec 17, 2019
@gbuktenica
Copy link
Author

Hi @SydneyhSmith I have just tried with the Preview Extension and I get the same behaviour.
I see you have tagged this issue with "Needs-Repro-Info". What more information is required?

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Dec 18, 2019
@SydneyhSmith
Copy link
Collaborator

@gbuktenica thanks for opening providing the steps, I am able to reproduce this...we are still investigating how to best resolve this issue--thanks!

@SydneyhSmith SydneyhSmith removed the Needs: Maintainer Attention Maintainer attention needed! label Dec 19, 2019
@TylerLeonhardt TylerLeonhardt changed the title Timed out waiting for the PowerShell extension to start. Timed out waiting for the PowerShell extension to start when Start debugging before extension starts Dec 20, 2019
@virovets64
Copy link

I have the same problem with v2020.4.0

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Apr 29, 2020
@gbuktenica
Copy link
Author

@virovets64 yes I still have the problem with

  • Operating System
    Windows 10

  • VS Code version
    1.44.2

  • PowerShell extension version
    2020.4.0

  • Output from $PSVersionTable

PSVersion 7.0.0
PSEdition Core

@TylerLeonhardt
Copy link
Member

I have a partial fix to this... pressing play with start the extension now, but it'll say you need to wait for it to finish starting.

At least it's two clicks of the same button, rather than opening a PS file.

@TylerLeonhardt TylerLeonhardt removed the Needs: Maintainer Attention Maintainer attention needed! label Apr 30, 2020
@andyleejordan
Copy link
Member

I think this has been fixed (and is about to be better fixed by #4888).

@andyleejordan andyleejordan added the Resolution-Fixed Will close automatically. label Jan 23, 2024
Copy link
Contributor

This issue has been labeled as resolved, please verify the provided fix (or other reason).

@github-actions github-actions bot added the Needs: Fix Verification Please verify the fix for us! label Jan 23, 2024
Copy link
Contributor

This issue has been labeled as needing fix verification and has not had any activity a week. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Debugging Issue-Bug A bug to squash. Needs: Fix Verification Please verify the fix for us! Resolution-Fixed Will close automatically.
Projects
None yet
Development

No branches or pull requests

5 participants