Fork me on GitHub
#cider
<
2019-11-04
>
bozhidar08:11:12

Thanks! :man-bowing:

bozhidar08:11:36

The survey made it to 300 responses over the weekend, let’s see if we can make it to 1300 (the number of the people in this channel) by the end of next weekend. 🙂 You can take it here https://forms.gle/Cp6DW2zGUQkh42u38

👍 4
pez08:11:04

Might be 1299 there, because I am a very special CIDER user who do not want to skew your survey results. 😃

tomd09:11:39

*cider-scratch* doesn't seem to be aware of the last-used repl buffer (unlike cljc files, which helpfully switch their evaluation focus depending on which repl (clj or cljs) you last had up). Since cider-toggle-buffer-connection was made obsolete, there seems to be no way to get *cider-scratch* to eval in cljs - it's just stuck on my clj repl. Is there something I'm missing, or is this a bug/feature that needs (re-)adding? Thanks!

deas12:11:10

Appears I'm lost ciders guts. 😢

deas12:11:01

Using it programmatically ending up

java.lang.NullPointerException
        at clojure.core$deref_future.invokeStatic(core.clj:2300)
        at clojure.core$deref.invokeStatic(core.clj:2320)
        at clojure.core$deref.invoke(core.clj:2306)
        at cider.nrepl$wrap_stacktrace$fn__7449.invoke(nrepl.clj:391)
        at nrepl.middleware$wrap_conj_descriptor$fn__5254.invoke(middleware.clj:16)
Guess it is the (@(get @delayed-handlers '~sym) ~handler ~msg))) from run-deferred-handler causing it. Appears to depend on the order things are loaded. Have two ways of lauching it. Both via lein, one works the other one ends up with the NPE.

bozhidar16:11:10

How exactly are you running it?

otfrom13:11:45

Is anyone still having trouble with this bug on cider latest? https://github.com/clojure-emacs/cider/issues/2621

otfrom13:11:56

attempting to debug this example:

(defn afew [x]
  (let [xs [\a \b \c \^]]
    (cycle xs)))

otfrom13:11:10

causes all my cpus to spin and CIDER debugger to hang

otfrom13:11:23

when it gets to evaluating cycle

bozhidar16:11:39

I haven’t seen any reports of this recently and I guess it’s fixed for @qythium as well.

yuhan16:11:58

yep, it's fixed for me since that PR linked in the issue

yuhan16:11:09

@otfrom maybe your cider-nrepl dependency is an older version, I think the latest 0.22.4 contains the fix

otfrom16:11:13

thx, probably my config then. I'll have a dig

bozhidar16:11:50

Btw, even with the fix you need to set some print limits. I think by default there are none.

deas18:11:14

We are shipping cider.nrepl with our app. It does not appear to play with AOT (e.g. delayed-handlers always empty). Am I missing something or is avoiding AOT the only way out?