vscode-powershell: F5 / Ctrl+F5 stops working while Run Active file in Active Terminal with Shift+CTRL+P works

Issue Description

Since some time now I often end up with F5, CTRL+F5 being unresponsive. It can happen right after VSCode start, after 1st run, after multiple runs. Totally random. In this case, I was able to run the code once, and subsequent F5 wouldn’t work. I can execute a script with SHIFT+CTRL+P and choosing Run active file in active terminal although I am not sure it’s the same thing.

Expected Behaviour

Shouldn’t bug out.

Actual Behaviour

debuggingstopsworking

Attached Logs

Don’t have logs for now, but I can try to get it. From earlier look at logs simply nothing happens when I press F5 or CTRL+F5. It’s like those commands get detached or something.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 6
Comments: 52 (28 by maintainers)

Most upvoted comments

@TylerLeonhardt I just updated my PowerShell extensions to 1.10.1 and it worked for me! Great job!

viloun on Dec 8, 2018

Ok I have a fix for this: https://github.com/PowerShell/PowerShellEditorServices/pull/807

I’m going to try to do a release today. 1.10.1

TylerLeonhardt on Dec 7, 2018

The same things, with ver. 1.10.0 F5 work only one time. Only with restart current session I can debug again. The usual Christmas gift from Microsoft…

maxmonterumisi on Dec 7, 2018

To downgrade to 1.9.0:

Download https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-vscode/vsextensions/powershell/1.9.0/vspackage
settings > “extensions.autoUpdate” : false
open the extensions sidebar, click on the ellipsis in the right upper corner, choose Install from VSIX.

ili101 on Dec 6, 2018

Rather than creating a new issue, and potentially having it be a duplicate of this one, I am adding a comment.

I also noticed this, but only after the recent upgrade to 1.10.0.

To reproduce… at least on my workstation… After upgrade to 1.10.0, Open a script. Press F5. Script executes and upon completion, exits debugging mode.

Even if making no changes, press F5 again, and it hangs. When it hangs, if on the debug view, at the top left of the screen, under the Configuration selector, a tiny blue bar runs across that part of the screen, and never stops. (Under normal circumstances, the bar is still there, but only briefly.)

To workaround, I have had to quit VS Code and open it again.

I tested by downgrading to 1.9, and could not reproduce the problem. Upgrade again to 1.10, and the problem happens again, every time.

dhoffman98 on Dec 6, 2018

Yeah, basically I want to see the expanded value of CurrentlyRunningCommand.

SeeminglyScience on Jan 10, 2019