Brandon Ringe

One option for a repro to test a solution is to use release `2023.04.19-12.43.29` of clojure-lsp and edit open/edit and edn file with a vector at the root that contains...

Thanks for the input. I too am not totally sure about avoiding all popups. The messages can at least be seen if the serverclient logs are turned on, so they...

> Closest thing is probably to write in the Calva says output channel. The errors are already printed in the clientserver logs channel. I don't think it's necessary to print...

@PEZ I don't think this is happening with `textDocument/publishDiagnostics`. You mentioned that in the linked issue but this particular issue is about errors like `Request textDocument/documentSymbol failed`, which isn't related...

I tried adding the following middleware to the lsp client to see if we could catch the error before the popup is shown: ```typescript async provideDocumentSymbols(document, token, next) { let...

We might be able to override `vscode.window.showErrorMessage` and filter out clojure-lsp errors.

Hmm... maybe to have a more reliable solution, we should just print the path somewhere for the user and let them open it however they want to.

Just to be more thorough, you can also check the developer console (Help -> Toggle Developer Tools -> Console tab) for errors, as well as [enable the logs between the...

@PEZ Could you take a look at this when you get a sec? I tried passing `'^a-test$'` but no tests are matched with that. I tried other things as well...

> I notice that CIDER uses the op test, and not test-var-query as Calva does. The `test` op is deprecated according to the cider-nrepl docs: https://docs.cider.mx/cider-nrepl/nrepl-api/ops.html#test