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

[PrzemyslawKlys]

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

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.

[dhoffman98]

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.

[Tuttu]

I support @dhoffman98 report. Yesterday, I was using version 1.9 of the module. Today, I have received the updated 1.10.0 version and now, I can't hit F5 to get my code running. I will only run the first time and then hang on.

As stated by @PrzemyslawKlys , using the "Run Active File in Active Terminal" solution works as a workaround.

[ili101]

To downgrade to 1.9.0:

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

[theRAAPster]

Same results as @dhoffman98 and @Tuttu. Was fine with the previous version, but started seeing this issue with version 1.10.0 where I only get one shot to run debugging. I did find that using the trash can to kill the Powershell Integrated Console would cause the extension to realize it terminated and it would ask to restart the console, which would allow another run of debugging. Adding some more info:

From EditorServices.log:

2018-12-06 10:48:12.832 [WARNING] tid:20 in 'DispatchMessage' C:\PowerShellEditorServices\src\PowerShellEditorServices.Protocol\MessageProtocol\MessageDispatcher.cs: line 147
MessageDispatcher: No handler registered for Event type '$/setTraceNotification'

Code version:

1.29.1
bc24f98b5f70467bc689abf41cc5550ca637088e
x64

Extensions:

bierner.color-info@0.5.0
CoenraadS.bracket-pair-colorizer@1.0.61
eamodio.gitlens@9.0.3
ms-python.python@2018.11.0
ms-vscode.PowerShell@1.10.0
PeterJausovec.vscode-docker@0.4.0
Shan.code-settings-sync@3.2.2

Editor Services Version:

Major Minor Build Revision
----- ----- ----- --------
1 10 0 0

PSVersionTable:

Name Value
---- -----
PSVersion 5.1.16299.785
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.16299.785
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

[PrzemyslawKlys]

To be honest I had this issue for at least a couple of weeks/months now. It used to be less common, now it's more common but I had this issue with 1.9.0 as well.

[TylerLeonhardt]

Thanks for the info! Can everyone attach the logs here so we can get a better idea of what's going on?

[PrzemyslawKlys]

1544116548-7ebc2a51-5bb2-4c3d-b5d2-694e610231711544086879684.zip

Hrms... indeed I can restart PowerShell session, run F5 once, and the subsequent session doesn't work.

[theRAAPster]

Logs attached
1544116464-98fc41e7-e0e2-4590-bf56-5c7bbdc5df781544116456476.zip

[TylerLeonhardt]

Thanks! It looks like I can repro this too. Let me investigate

[Tuttu]

Do you need more logs @TylerLeonhardt ?

[SydneyhSmith]

@Tuttu We can always use more logs, thank you!

[viloun]

I had issues with 1.10 and also 1.9. I actually went all the way back to 1.8.3 and it works. I'm going to leave it at 1.8.3 until the latest version gets fixed. My vscode is at 1.29.1