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
Exception when close all working files and some are dirty #4253
Comments
@isidorn do you get the dialog prompting you to save dirty files before the exception or after? |
I get the dialog and I say 'do not save' - can not always repro, can you please try it out a couple of times |
I dont even know what that handler is as it seems in the extension host, moving to @jrieken / @alexandrudima |
@isidorn Can you reproduce without installed extensions? |
@alexandrudima I can repro it if I do not have any extensions installed |
@isidorn The steps don't do it for me, also the message appears nowhere in our sources. Please attach the debugger to the extension host and break on error such that we have a chance to understand this |
@dbaeumer Maybe you use such strings in the language protocol? |
@jrieken when I attach debugger to the extension host I can not seem to get it to break on this error. |
@isidorn Sure you don't have PowerShell tools installed? https://github.com/PowerShell/PowerShellEditorServices/blob/9fa1feaf16d13075c02b420789bbebe9b75c122b/src/PowerShellEditorServices.Protocol/LanguageServer/TextDocument.cs#L59 |
harding @alexandrudima assumption about the language protocol (https://github.com/Microsoft/vscode-languageserver-protocol/blob/46dd8c99166b3cbee69a54e6043b99be221d793c/README.md#L654) |
@jrieken I do not have powershell installed |
maybe tslint? |
I do not have any extensions installed :) |
Yes you have. It's called JSON and uses the language server protocol. Moving to @dbaeumer cos this seems to come from |
The protocol calls a notification handler which causes an exception. The protocol on the lowest level catches the excpetion sends it back to the client which prints it to the console. There is nothing I can do better. The root cause of the exception must be fixed. The root cause lies in the languge server. I receive an update event for a document that is already closed. The interesting question is why? But I will protect my code against it. |
This issue was moved to microsoft/vscode-languageserver-node#28 |
Published 1.4.1 of the language server. |
Steps to Reproduce:
edited: first exception that I now removed was caused by an unrelated issue
The text was updated successfully, but these errors were encountered: