It’s probably to do with how VS Code is updating the clojure-lsp server. You can try reproduce it in a minimal file while observing the clojure-lsp message logging.

What do you mean by updating the clojure-lsp server?

I’m thinking that when the file changes, the clojure-lsp server needs to know this and that if this update doesn’t happen, then the analysis will be on the old content.

Even after I make further changes to this file, save it, etc - the message is still here.

Have you checked the clojure-lsp message log?

I don't see such output tab.

Check your clojure.trace.server setting.

I should look at this one?

Yes, that’s the one. (Though I do not know what to expect to be there, but maybe we can form a hypothesis from what we see there.)

Log is not really helpful for me without background, but my guess is:

• Calva asks LSP for info about currently edited symbol • LSP responds with, for example, invalid symbol json/read-tr • After the fix is made, Calva repeats the ask for this symbol, no errors returned this time but old message is still left there.

All the errors I am seeing are errors from last edit before the fix.

It’s not really Calva doing this. Calva role is that it introduces VS Code and clojure-lsp: “Hi VS Code, say hello to clojure-lsp. clojure-lsp, this is VS Code.” And then Calva leaves the conversation and lets them talk to each other. This is probably VS Code failing to invalidate some cache properly. See if you can find any issues about it on the vscode repository. It probably isn’t Calva/clojure-lsp specific.

One more thing you can check is if the Problem pane has the error. If not, it could be Error Lens that is the problem.

Yeah, definitely. It's also failing in non-clojure files.