Fork me on GitHub
#calva
<
2022-09-19
>
skylize00:09:16

Running npm i on the dev branch gives me 5 moderate severity vulnerabilities. Any reason we can't let npm fix that for us with npm audit fix?

pez19:09:55

Thanks for bringing this up. The reason is usually that we have run fix and it hasn't fixed it. Then we wait a bit. Now I ran it and we're clean again.

craftybones00:09:14

Getting an error with the latest Calva:

[Error - 6:28:27 AM] Request textDocument/codeAction failed.
  Message: Internal error
  Code: -32603 
[object Object]

craftybones00:09:33

It pops up a little while after I jack in and begin writing code

craftybones01:09:06

All I have is this

(ns measure)

(def units {:units.length/inch {:factor 1}
            :units.length/foot {:factor 12}})

(defn is-unit-of [unit]
  (and (units unit)
       ()))

craftybones01:09:33

Evaluation etc still work. Just get the error and a popup

craftybones01:09:03

Rolling back to a version 2 weeks ago still gives me the error

skylize01:09:07

It's an upstream bug in Clojure LSP. Just fixed today in nightly build. You can either change "Clojure Lsp Version" setting in Code to "nightly" to get the latest build, or just wait for next LSP release.

pez06:09:52

Dear Calva friends calva We managed yet another release yesterday. https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.303 • Fix: https://github.com/BetterThanTomorrow/calva/issues/1869 So now , even if you are on an M1 Mac, when @ericdallo asks you to try something out with the latest dev/nightly build, you can just set calva.clojureLspVersion to nightly and restart the clojure-lsp server (using the status bar button if you like). Personally I will try to stay on nightly most of the time, to be able to help the clojure-lsp team with early testing.

🎉 5
🚀 4
gratitude 3
bringe02:09:54

Switched mine to nightly as well!

metal 2