This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-11
Channels
- # announcements (15)
- # aws (11)
- # babashka (13)
- # babashka-sci-dev (2)
- # beginners (63)
- # calva (20)
- # cider (9)
- # clj-kondo (27)
- # clojars (3)
- # clojure (34)
- # clojure-art (4)
- # clojure-europe (21)
- # clojure-filipino (1)
- # clojure-indonesia (1)
- # clojure-my (1)
- # clojure-nl (11)
- # clojure-norway (10)
- # clojure-sg (1)
- # clojure-spec (4)
- # clojure-uk (4)
- # clojurescript (5)
- # cursive (8)
- # deps-new (2)
- # events (1)
- # exercism (2)
- # fulcro (44)
- # graphql (6)
- # gratitude (1)
- # introduce-yourself (1)
- # jobs (3)
- # leiningen (5)
- # lsp (26)
- # membrane (18)
- # missionary (9)
- # off-topic (1)
- # pedestal (5)
- # portal (1)
- # quil (24)
- # re-frame (17)
- # reagent (5)
- # remote-jobs (2)
- # reveal (3)
- # spacemacs (4)
- # tools-build (1)
- # tools-deps (12)
@ramblurr No, there's no. It's kind of hard to decide where exactly a new test should go within a test ns, but if you have concrete ideas feel free to open a feature request ticket.
@ramblurr If your assumptions match mine, you can use the code here: https://github.com/magnars/.emacs.d/blob/master/defuns/clj-defuns.el#L50
Hello everyone, I recently started getting this error when ever I get a runtime error. Does anyone know what may be going on?
PS: the error buffer appears rarely now, and I get most errors directly on the repl buffer.
PS2: seems like it may be a problem with a single specific repository, but it’s the one I have been mainly working on, so it’s hard tell with 100% certainty. But if it was the case, we are using mulog
and that seems to interact with logging in some ways.
Execution error (IndexOutOfBoundsException) at my.namespace/eval66596 (REPL:204).
null
ERROR: Unhandled REPL handler exception processing message {:nrepl.middleware.print/stream? 1, :nrepl.middleware.print/print cider.nrepl.pprint/pprint, :nrepl.middleware.print/quota 1048576, :nrepl.middleware.print/buffer-size 4096, :nrepl.middleware.print/options {:right-margin 80, :length 80, :level 20}, :op stacktrace, :session f81c5e6b-a4be-47fc-9573-7e3c532e4e06, :id 394}
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Cannot open <nil> as a Reader.
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at clojure.core$deref_future.invokeStatic(core.clj:2300)
at clojure.core$future_call$reify__8454.deref(core.clj:6974)
at clojure.core$deref.invokeStatic(core.clj:2320)
at clojure.core$pmap$step__8467$fn__8471.invoke(core.clj:7025)
at clojure.lang.LazySeq.sval(LazySeq.java:42)
at clojure.lang.LazySeq.seq(LazySeq.java:51)
at clojure.lang.RT.seq(RT.java:535)
at clojure.core$seq__5402.invokeStatic(core.clj:137)
at clojure.core$filter$fn__5893.invoke(core.clj:2809)
at clojure.lang.LazySeq.sval(LazySeq.java:42)
at clojure.lang.LazySeq.seq(LazySeq.java:51)
at clojure.lang.Cons.next(Cons.java:39)
at clojure.lang.RT.length(RT.java:1784)
at clojure.lang.RT.seqToArray(RT.java:1725)
at clojure.lang.LazySeq.toArray(LazySeq.java:132)
at clojure.lang.RT.toArray(RT.java:1698)
at clojure.core$to_array.invokeStatic(core.clj:344)
at clojure.core$sort.invokeStatic(core.clj:3113)
at clojure.core$sort.invokeStatic(core.clj:3102)
at clojure.core$sort.invoke(core.clj:3102)
at cider.nrepl.inlined_deps.orchard.v0v9v0.orchard.namespace$classpath_namespaces.invokeStatic(namespace.clj:119)
at cider.nrepl.inlined_deps.orchard.v0v9v0.orchard.namespace$classpath_namespaces.invoke(namespace.clj:106)
at cider.nrepl.inlined_deps.orchard.v0v9v0.orchard.namespace$project_namespaces.invokeStatic(namespace.clj:131)
at cider.nrepl.inlined_deps.orchard.v0v9v0.orchard.namespace$project_namespaces.invoke(namespace.clj:123)
...
Hi @U7AMPCPU2 I'm the author of μ/log and I use cider as well for my development and I never seen this error. I agree with @U45T93RA6, by the message it looks like a version mismatch between cider and cider-nrepl. however should the error persist, I'll be happy to help you to debug and check whether mulog is the cause of to rule it out.
Thanks a lot @U45T93RA6 and @U0LCHMJTA. Appreciate your help. I’ll update ASAP and will let you know if the issue persists.