-
Notifications
You must be signed in to change notification settings - Fork 510
While typing in a file, NullReferenceException in ReferencesCodeLensProvider hangs language server #857
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
I'm seeing an issue where the Pester CodeLenses disappear from the document. Assuming it's due to this same issue, correct? |
When the Pester lenses disappear do you see any exception in the logs? |
It appears to be the same one posted here. Tough to get an exact timestamp correlation, but it looks like the only significant error I see. There are a few other errors, but they appear to be happening around startup:
|
This change fixes an issue where a null case isn't being handled gracefully in the ReferencesCodeLensProvider when resolving a CodeLens while the user is typing out a new function defintion or doing anything else that causes the code to change like formatting the script. Resolves PowerShell/vscode-powershell#857 Resolves PowerShell/vscode-powershell#855
This change fixes an issue where a null case isn't being handled gracefully in the ReferencesCodeLensProvider when resolving a CodeLens while the user is typing out a new function defintion or doing anything else that causes the code to change like formatting the script. Resolves PowerShell/vscode-powershell#857 Resolves PowerShell/vscode-powershell#855
Need a general way to catch exceptions coming from feature providers so that they don't take down the language server when they misbehave.
The text was updated successfully, but these errors were encountered: