This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-04
Channels
- # announcements (8)
- # beginners (27)
- # calva (8)
- # cider (26)
- # clara (19)
- # cljdoc (4)
- # cljsjs (1)
- # clojure (221)
- # clojure-dev (6)
- # clojure-europe (11)
- # clojure-gamedev (18)
- # clojure-italy (8)
- # clojure-nl (12)
- # clojure-spec (85)
- # clojure-uk (17)
- # clojurescript (34)
- # community-development (1)
- # cursive (26)
- # datomic (16)
- # dirac (19)
- # duct (6)
- # editors (4)
- # figwheel-main (1)
- # fulcro (68)
- # graphql (41)
- # juxt (16)
- # luminus (11)
- # off-topic (30)
- # pathom (35)
- # planck (2)
- # re-frame (18)
- # reagent (20)
- # remote-jobs (6)
- # rum (1)
- # shadow-cljs (37)
- # spacemacs (9)
- # vim (14)
how do I prevent the cider debugger from trying to fully realize lazy sequences?
(let [n 5]
#dbg
(take (inc n) (repeat n)))
this hangs indefinitely trying to evaluate (repeat n)
whereas eg. cider-eval on an infinite sequence doesn't have that issue@qythium I’ll have to take a look at the code to be sure, but I assume the debugger might be doing a sync eval would be stuck forever once the result starts coming.
Thanks, I thought it might be something obvious I was missing, but it sounds more like a bug - will file an issue on the Cider repo sometime later 🙂
@malabarba would know better if he’s around.
> @frozenlock just a note that I haven’t seen pretty printing working in shadow-cljs
@richiardiandrea But the printing logic is independent from ClojureScript, so I can’t imagine how this won’t be working. We get the value from ClojureScript, but we pretty-print it in Clojure.
Ok i quali try to take the time and do it
Btw, a few random updates from me https://metaredux.com/posts/2019/04/03/meta-reduce-volume-2019-0.html
cider-nrepl's stacktrace
op has became freakishly slow.
Some stacktraces take as long as 5-10 seconds to render.
I profiled it to discover that most cost is paid for resolving each frame to a Java class/method.
Is this all really necessary, or is it possible to cut down some of that?
@alexyakushev I don’t remember to be honest. We have barely touched it since it’s initial version. And I don’t recall any recent changes that’s why I’m puzzled by your observation that it has suddenly become very slow.
Digging deeper, looks like it is connected to the fact this is a Java/Clojure project, and orchard has some special rules to when not to cache internal Java classes.
I have many internal classes on the stacktrace, and they are being parsed over and over.
I'll try to do something about this case
I was just about to cut a new Orchard release, so now is a good time to tackle this.
By the way, that could be the reason why my tests were hanging the other day.
The tests were failing with exceptions and there were ~100 of them, so CIDER was probably busy rendering the stacktraces.
@alexyakushev Check out the new cider-nrepl snapshot.
Yes, thanks, seems to be working.
I finally had to restart the REPL 🙂