-
Notifications
You must be signed in to change notification settings - Fork 513
Debugger stopped working after upgrading vscode to 1.0 #149
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
Comments
Hey Flavio, 1.0 appears to have changed some things that might have broken our debug adapter. Thanks for sending along the logs! |
Another hit: microsoft/vscode#5429 |
BTW the updated debug protocol for 1.0.0 says this:
We may need to merge that ordering change PR to a 0.5.1 branch and post it. |
I believe I have the same issue. When starting the debugger, nothing happens. However, if I set a breakpoint, everything runs as expected. |
Sorry for the trouble guys, we'll get a new update out to fix this in the next few days. |
This is verified to be fixed in the 0.6.0 version of the extension, coming out very soon. I'll close this bug once the update has been shipped. Thanks for your patience! |
0.6.0 is now released! Let me know if you run into any further trouble. |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone
As the title says, my previously working setup suddenly stopped doing anything after the upgrade. I can see the the Microsoft.PowerShell.EditorServices.Host.exe process running in the background, but the GUI just waits forever for any output. Unfortunately I can't find any error messages in the log files which makes this very hard to track. Could anyone point me into the right direction? Thanks!
The text was updated successfully, but these errors were encountered: