I frequently get an error pop-up while writing Deno in VS Code, for example when pressing Command-Period, but also at other times (I think). It says: "Request textDocument/codeAction failed." This prevents any code actions from working.
If I look in the Deno LSP output, I see a bunch of these:
It seems that an assumption that the LSP is making when running a regex on a code action is not holding.
To Reproduce
I don't know steps for someone to reproduce it, but if there's some way to get debugging information about what's happening (like what are the code actions that can't be parsed?) I'd be happy to try it.
Describe the bug
I frequently get an error pop-up while writing Deno in VS Code, for example when pressing Command-Period, but also at other times (I think). It says: "Request textDocument/codeAction failed." This prevents any code actions from working.
If I look in the Deno LSP output, I see a bunch of these:
This error message is not hard to find in the LSP codebase: https://github.com/denoland/deno/blob/cead8af104af693558db07675a423761f174d260/cli/lsp/analysis.rs#L622
It seems that an assumption that the LSP is making when running a regex on a code action is not holding.
To Reproduce
I don't know steps for someone to reproduce it, but if there's some way to get debugging information about what's happening (like what are the code actions that can't be parsed?) I'd be happy to try it.
Expected behavior
No error pop-up, code actions work.
Versions
vscode: 1.94.0 deno: 2.0.2 extension: v3.42.0