This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-19
Channels
- # announcements (4)
- # aws (9)
- # babashka (1)
- # beginners (41)
- # cider (13)
- # clojure (45)
- # clojure-europe (16)
- # clojure-hungary (3)
- # clojure-norway (6)
- # clojure-uk (6)
- # clojurescript (14)
- # clr (3)
- # css (1)
- # datalevin (2)
- # datomic (2)
- # fulcro (8)
- # introduce-yourself (6)
- # jobs (3)
- # malli (2)
- # nbb (49)
- # off-topic (3)
- # reitit (23)
- # shadow-cljs (36)
- # tools-deps (2)
Hallo. I have a problem seeing exceptions when evaluating in buffer.
I am connected to shadow-cljs with a runtime on Google Firebase Functions emulator. I can evaluate in REPL and in buffers. Here is an example: When I evaluate in the REPL, I get the following output:
Execution error (TypeError) at (<cljs repl>:1).
shadow.js.shim.module$twilio.default is not a function
;; => :repl/exception!
Which is what I need. But when I evaluate in the buffer, I only see the result, which is :repl/exception and I can not see the error itself. Is there a way to make the error visible somewhere when I eval in buffer? Thank you!
normally the full error is printed to the console, so it should be somewhere in the emulator logs?
but cider seems the hide the error for some reason. someone else asked about this not too long ago
It's more likely that it gets printed in the nREPL server buffer or something like this. CIDER definitely doesn't do anything to hide some of the error output that would normally end up the REPL. The output bindings can get messy.
@U2ERGD6UD FWIW the error above means that you probably used (require '["twilio$default" :as x]) or (require '["twilio" :default x]) or via ns and then (x ...) somewhere. but x wasn't actually a function.
@U05224H0W Thank you. I figured this out. But this was not the point of my question here. I have the problem with the missing exception contents all the time. Every time I eval something in a buffer and it fails, I have no idea what it is, because I only see :repl/exception , as output after the eval. Which is completely useless. I would like to see the error instead. The exception itself. But this is only visible when I evaluate in the CIDER-REPL.
So I think this is a CIDER problem. Because it shows the error when evaluating in CIDER-REPL, but swollows it, when evaluating in a buffer.
I mean the REPL that CIDER provides after connected. It probably is just the emacs buffer which allows interaction with the REPL.
@U051BLM8F I tried to simplify the problem. I will try to explain:
When I evaluate (println "hello") in the buffer, I get ==> nil as output in the buffer. And I can see hello printed into the REPL (in emacs).
When I evaluate (throw (js/Error. "boom")) in the buffer, I get ==> :repl/error as output in the buffer. And NOTHING is printed into the REPL.
But when I evaluate (throw (js/Error. "boom")) in the REPL, then the error IS printed into the REPL.
So it seams a successful evaluation from a buffer "happens" in the REPL, while a failed evaluation does not.