This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-03
Channels
- # aws (27)
- # beginners (64)
- # boot (14)
- # calva (10)
- # cider (36)
- # cljs-dev (13)
- # cljsrn (79)
- # clojure (58)
- # clojure-berlin (8)
- # clojure-france (1)
- # clojure-italy (18)
- # clojure-nl (9)
- # clojure-russia (1)
- # clojure-spec (28)
- # clojure-uk (29)
- # clojurescript (55)
- # core-async (20)
- # cursive (5)
- # datomic (105)
- # emacs (17)
- # figwheel-main (13)
- # fulcro (20)
- # graphql (4)
- # hoplon (1)
- # hyperfiddle (2)
- # jobs (7)
- # jobs-discuss (110)
- # off-topic (23)
- # pathom (1)
- # perun (2)
- # re-frame (87)
- # reitit (2)
- # shadow-cljs (8)
- # spacemacs (2)
- # tools-deps (118)
- # vim (11)
I upgraded to the latest cider version (0.20.0snapshot (package: 20190103.619)) and now I'm getting this warning:
;; CIDER 0.20.0snapshot (package: 20190103.619), nREPL 0.2.12
;; Clojure 1.10.0, Java 1.8.0_171
...
WARNING: CIDER requires nREPL 0.4.4 (or newer) to work properly
More information.
WARNING: CIDER requires cider-nrepl to be fully functional. Many things will not work without it!
More information.
I don't have any cider specific dependency in my profiles.clj
- I thought it would inject the proper deps automatically
If that matters, I've also upgraded to the latest lein 2.8.3
Leiningen 2.8.3 on Java 1.8.0_171 Java HotSpot(TM) 64-Bit Server VM
I am using cider version 0.19.0 and when I try to integrate figwheel
on it, I receive a Stdin
prompt waiting me to type something
I tried to cider-jack-in
regularly on a .cljs
buffer and then used the
(require 'figwheel-sidecar.repl-api)
(figwheel-sidecar.repl-api/start-figwheel!)
(figwheel-sidecar.repl-api/cljs-repl)
I did a clean start from cider, lein and my repo. The resulting error message was:
nREPL server started on port 60859 on host localhost -
ERROR: Unhandled REPL handler exception processing message {:op clone, :id 1}
java.lang.NullPointerException
at clojure.core$deref_future.invokeStatic(core.clj:2208)
at clojure.core$deref.invokeStatic(core.clj:2228)
at clojure.core$deref.invoke(core.clj:2214)
at cider.piggieback$wrap_cljs_repl$fn__2262.invoke(piggieback.clj:274)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_version$fn__2986.invoke(nrepl.clj:509)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_pprint$fn__2796.invoke(nrepl.clj:120)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_apropos$fn__2822.invoke(nrepl.clj:159)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_format$fn__2864.invoke(nrepl.clj:223)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_enlighten$fn__2856.invoke(nrepl.clj:219)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_refresh$fn__2922.invoke(nrepl.clj:388)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at cider.nrepl$wrap_spec$fn__2938.invoke(nrepl.clj:426)
at clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1894.invoke(middleware.clj:22)
at nrepl.server$handle_STAR_.invokeStatic(server.clj:18)
at nrepl.server$handle_STAR_.invoke(server.clj:15)
at nrepl.server$handle$fn__888.invoke(server.clj:27)
at clojure.core$binding_conveyor_fn$fn__4676.invoke(core.clj:1938)
at clojure.lang.AFn.call(AFn.java:18)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
I am using the lein re-frame template with +cider option. No further dependencies in the project. Just run lein new re-frame testCider +cider
Getting an error with the latest cider when evaling with error messages like this "No such namespace: cider.nrepl.pprint"
I'm using ~/.clojure/deps.edn
like this:
{:aliases {:nrepl {:extra-deps {nrepl {:mvn/version "0.6.0-SNAPSHOT"}}}
:cider {:extra-deps
{cider/cider-nrepl {:mvn/version "0.20.0-SNAPSHOT"}
refactor-nrepl {:mvn/version "2.4.0"}}}}}
invoked with clj -R:nrepl:cider dev.clj
is this a proper way to do different things depending on the cider version?
(setq cider-minor-version (second (pkg-info-library-version 'cider)))
(defun clojure-repl? ()
(cond ((eq cider-minor-version 18) (equal cider-repl-type "clj"))
((> cider-minor-version 18)) (eq cider-repl-type 'clj)
(t (error "Cider version not supported"))))
and another thing, I'm not sure if I'm the only one but I find it quite strange sometimes that when you start Repls you don't get any feedback until they are up and running
and in projects where it takes a long time you can end up for a while not knowing if it started correctly or not (or if it's starting at all).
Sometimes I switch to the nrepl
buffer to see what is going on, but is there another way maybe?
You can also use (member '(clj "clj"))
, which seems better to me than a version check.
> and another thing, I’m not sure if I’m the only one but I find it quite strange sometimes that when you start Repls you don’t get any feedback until they are up and running
yes I saw cider-version
and at first I used string-match
on that @bozhidar
but then I saw that i can get the actual minor version number directly with that so I thought it was better
I'll try the member thanks for the suggestion
related to the REPL, well yes I know that when it works you get the REPL(s), but sometimes on big projects it takes 1 minute until you get it
and until then you have no idea if it's actually starting at all
unless you check the nrepl buffer
I think you also get a message that CIDER is starting up and this can take a while, but I see your point.
Unfortunately I can’t think of any meaningful way to show some progress - basically CIDER just sits and waits to see the message that an nREPL server has been booted, so it can connect to it.
well @bozhidar there could just be something small spinning in the modeline for example
The problem is that it will keep on spinning in case of some startup error as well. 🙂 Still, you make a reasonable point.
I wonder if https://github.com/clojure/tools.analyzer.js is worth rescuing? as @benedek says here https://github.com/clojure-emacs/clj-refactor.el/issues/191#issuecomment-244399946 it seems to block rich features. Is the observation still valid? This could be a nice pet project for me. Another possibility could be to crowdfund it (as I'm not sure I have the availability for such an undertaking; would be happy to pay for it instead) cc/ @bronsa
Well, given the fact that no one has had any bandwidth for the clj-refactor for over a year I think that’s the least of our concerns.