Closed CendioOssman closed 6 months ago
This looks like an issue I've seen reported elsewhere (vscode-restructuredtext/vscode-restructuredtext#433) and (vscode-restructuredtext/vscode-restructuredtext#429)
The TL;DR is that a common pattern in VSCode extensions when reporting a diagnostic that includes the end of the line, is to set the column number to a very large value, well outside the range allowed by the language server protocol ([0:2147483647]
). When asking esbonio
for any available code actions, VSCode includes all diagnostics in your project as additional context, leading to the situation where any VSCode extension has the opportunity to accidentally break the server.
I keep meaning to push an update to make the server less pedantic about these issues, hopefully now that there's an issue in this repo to remind me, I can get something out sooner rather than later :sweat_smile:
0.16.4
of esbonio
is now available with a patch that should hopefully fix the issue you are seeing
Thanks for your quick attention!
I upgraded to 0.16.4, and I'm no longer getting any crashes on the files it previously complained about. :)
Glad to hear it! :)
I'm getting this crash when parsing one of our files:
This is via vscode-ltex. All it says at its end is:
Unsure what you need to debug this, so please let me know how to proceed.