This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-14
Channels
- # announcements (4)
- # aws (7)
- # babashka (44)
- # beginners (178)
- # calva (15)
- # cider (3)
- # clj-kondo (15)
- # clojure (139)
- # clojure-dev (8)
- # clojure-europe (2)
- # clojure-italy (2)
- # clojure-losangeles (9)
- # clojure-nl (32)
- # clojure-spec (6)
- # clojure-sweden (1)
- # clojure-uk (27)
- # clojurescript (17)
- # core-typed (116)
- # cursive (26)
- # data-science (1)
- # datomic (14)
- # duct (16)
- # emacs (9)
- # events (1)
- # fulcro (47)
- # jobs (3)
- # juxt (6)
- # keechma (2)
- # malli (59)
- # mid-cities-meetup (8)
- # off-topic (32)
- # pathom (5)
- # reagent (2)
- # remote-jobs (4)
- # rewrite-clj (16)
- # shadow-cljs (14)
- # spacemacs (9)
- # sql (27)
- # tools-deps (37)
- # vscode (7)
I am working on a web app where the debugger often stops after I have had one round of debugging (C-u C-M-x, load web page, debug function, load web page, debugger doesn't work anymore). I saw the issue here and added a comment: https://github.com/clojure-emacs/cider-nrepl/issues/460 However I am missing a nice minimal reproduction case.
Can anyone advise me on how to gather information on the "health" of the debugger, so that I can at least make a more meaningful report?
Here are a couple of aberrant cases summed up: https://github.com/clojure-emacs/cider/issues/2796