This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-08
Channels
- # aleph (9)
- # announcements (42)
- # babashka (13)
- # babashka-sci-dev (9)
- # beginners (38)
- # biff (1)
- # calva (4)
- # cider (5)
- # clj-kondo (39)
- # cljdoc (4)
- # cljsrn (3)
- # clojure (93)
- # clojure-bay-area (1)
- # clojure-czech (1)
- # clojure-dev (4)
- # clojure-europe (65)
- # clojure-finland (3)
- # clojure-nl (2)
- # clojure-norway (7)
- # clojure-portugal (1)
- # clojure-uk (2)
- # clojurescript (73)
- # cloverage (1)
- # cursive (5)
- # data-science (1)
- # datahike (22)
- # emacs (51)
- # graalvm (6)
- # introduce-yourself (8)
- # jobs-discuss (14)
- # kaocha (6)
- # mount (5)
- # nbb (19)
- # off-topic (19)
- # reagent (5)
- # releases (1)
- # sci (19)
- # scittle (4)
- # shadow-cljs (6)
- # tools-deps (9)
- # xtdb (2)
This npx nbb nrepl-server :port 8001
seems to crash when I connect to it using IntelliJ remote REPL. The trace is in the crash-trace.txt attachment. It tries to look for Tk [Error]: Unable to resolve classname: java.io.PrintWriter
Any ideas?
@adam.kalisz You should take this up with #C0744GXCJ’s maintainer. I think there might already be an issue about nbb. Nothing nbb can do here really, it's cursive that assumes a JVM on the other end
If you're willing to try #CBE668G4R as one of the closest things to IntelliJ, it has good support for nbb
Thanks for the quick reply and suggestions. I would expect, it wouldn't crash 🙂
That is ok, but IMHO a connection made in error shouldn't crash the program - it should perhaps produce a trace/ log a warning or something 🙂 Thank you for your patience!