This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-19
Channels
- # announcements (5)
- # asami (7)
- # aws (10)
- # babashka (10)
- # beginners (49)
- # calva (12)
- # cider (5)
- # circleci (1)
- # clj-kondo (25)
- # clj-yaml (14)
- # clojars (5)
- # clojure (134)
- # clojure-europe (142)
- # clojure-france (3)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojurescript (10)
- # cursive (8)
- # datomic (19)
- # emacs (11)
- # fulcro (8)
- # graalvm (29)
- # honeysql (7)
- # jobs (4)
- # jobs-discuss (9)
- # lsp (196)
- # obb (4)
- # off-topic (40)
- # pathom (4)
- # releases (4)
- # remote-jobs (3)
- # shadow-cljs (16)
- # sql (25)
- # squint (2)
- # tools-deps (12)
- # xtdb (7)
- # yada (4)
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
?
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.
Getting an error with the latest Calva:
[Error - 6:28:27 AM] Request textDocument/codeAction failed.
Message: Internal error
Code: -32603
[object Object]
It pops up a little while after I jack in and begin writing code
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)
()))
Evaluation etc still work. Just get the error and a popup
Rolling back to a version 2 weeks ago still gives me the error
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.
Cool. Thanks
Dear Calva friends 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.