You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use a breakpoint, run code with F5 and wait for it to hit a breakpoint, and then use F8 to run code within Visual Studio Code - debugging will continue instead of doing nothing. I am not sure when it went bonkers, but I just noticed it now. It used to work fine.
I'm curious, does this problem go away if we write a line after invoking readline if the task has been canceled?
See this part of the change (which was what allowed us to "re-use" the existing prompt for F5 and F8 input):
But this is just a guess based on F8 being included in the text :)
Edit: After speaking to @SeeminglyScience it seems to be related to:
Prerequisites
Summary
If you use a breakpoint, run code with F5 and wait for it to hit a breakpoint, and then use F8 to run code within Visual Studio Code - debugging will continue instead of doing nothing. I am not sure when it went bonkers, but I just noticed it now. It used to work fine.
My suspect is related to:
WriteWithPrompt()
PowerShellEditorServices#1781But this is just a guess based on F8 being included in the text :)
Edit: After speaking to @SeeminglyScience it seems to be related to:
InterruptCurrentForeground
andMustRunInForeground
PowerShellEditorServices#1777PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
Visuals
Logs
No response
The text was updated successfully, but these errors were encountered: