-
Notifications
You must be signed in to change notification settings - Fork 510
Hangs on ArgumentCompleter Debugging #3256
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
Same problem here 🙁 |
@JustinGrote Do you know if this continues to repro with the latest Preview? @babysnakes What version of the extension are you using? |
@andschwa , I'm using current latest ( Thanks EDIT: forgot to mention, I'm using PowerShell 7.2 on windows 10. |
@babysnakes Can you try the latest version of PowerShell Preview for VS Code? Thanks again! |
@andschwa sure, I'll try tomorrow and update. |
@andschwa, Sorry it took me some time 🙁 ... I installed the latest preview, Imported the completion from file and tried to debug completions. The good news is that I was able to step the debugger. It doesn't seem to produce completion back to the terminal but it's a good start 😄. Here's the entire output from the terminal:
|
Ah ha, that's super useful @babysnakes, it looks like the same thing we're seeing in #3751. Seems like the way we're invoking PSReadLine barfs if it happens under the debugger while it's in the middle of doing something. |
@andschwa , glad I could help. Let me know if there's anything else you want me to try. |
Ditto #3751 (comment) @babysnakes and @JustinGrote. Can you try again? |
Marking as fixed, if it does still repro, please let me know, and re-open it! |
This issue has been marked as fixed. It has been automatically closed for housekeeping purposes. |
@andschwa, I don't see any new plugin version (or github release). The last one is from over a week ago (02/02/22 - |
Yes, that version of the PowerShell Preview extension is what I tested. It has the fix I mentioned (PowerShell/PowerShellEditorServices#1690) and I can no longer repro this bug report (where I could previously). |
@andschwa, here's the output from the debugging completion terminal. It's similar to before. Note that the current state of debugging completion script is good enough for me. I don't need the output to be printed to the console:
|
@babysnakes Can you share the script you're debugging that's causing that? |
Ah ha, on pressing Continue it errors:
|
@andschwa yeah, sorry, I didn't explain myself correctly ... |
No worries! That's why it's helpful to have enough repro info for me to step through it all. This helps narrow it down. I'll get a debugger attached and see what's happening when I press "Continue" that ReadLine barfs. |
Example Code:
When dotsourcing this from a file and then starting interactive debug with F5, upon attempting the completion it starts debug and stops at the correct line and displays all the info, however the console is hung and none of the debug buttons (run, step into/out/etc) work. Stop does work, but the integrated console totally hangs and requires a restart.

The text was updated successfully, but these errors were encountered: