-
Notifications
You must be signed in to change notification settings - Fork 494
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
Intellisense loss after debugging #2364
Intellisense loss after debugging #2364
Comments
(Note: eventually debugging comes back. @PrzemyslawKlys mentioned it might be a consequence of interacting with/cancelling the prompt) |
Can't repro on macOS with a local build - can you try a local build? |
@TylerLeonhardt have you seen: #2439 - it's quite easy to reproduce. |
The repro steps are the same right @PrzemyslawKlys? |
Hrmm, seems so. Have any code, press F5, any IntelliSense for parameters on next try doesn't work. Press Enter in console and everything works. So pressing F5, pressing Enter in console is the proper way to continue straight away. Or simply wait for "timeout" to happen (however not sure how long that is). |
Yeah it looks like it's fixed in my local build unless there's a mac and windows behavior difference which is totally possible. |
I'll take a look today on my machine |
So the root cause here is that the DisconnectHandler asks the PowerShellContextService to abort execution, which sets the session state to The problem now is that we need to understand why these session state concepts exist and what the cleanup from the aborted state is supposed to look like |
Get-<Tab>
belowFrom the message log:
It seems that the PowerShellContextState isn't being set properly and so completions get skipped for some time after debugging has ended.
The text was updated successfully, but these errors were encountered: