Fork me on GitHub
#calva
<
2021-11-12
>
Jakub Holý10:11:49

Hi! when a clojure.test test fails with an exception, is there a way to see its stack trace? I only get this in the repl > ; ERROR in clj-concordion.features-test/i-fail (line 23): > ; Uncaught exception, not in assertion > ; error: clojure.lang.ExceptionInfo: fake {} (features_test.clj) > ; expected: > (throw (ex-info fake {})) > ; 1 tests finished, problems found. 😭 errors: 1, failures: 0, ns: 1, vars: 1 I'd like to see the stack trace... According to https://github.com/clojure/clojure/blob/master/src/clj/clojure/test.clj#L384 it should print the stack trace but my output stops after the "expected" part and the "actual" and stack trace are missing. In CLI (`lein test` ) I get the stack trace... There is nothing useful at https://calva.io/test-runner/ ...

pez11:11:50

I think this might be a an omission we should fix.

👍 1
🙏 1
pez11:11:12

Curious, do you have the trace in *e at that point?

pez11:11:55

Please file an, issue, btw. 😃

👍 1
Stefan14:11:20

Now that I’m drooling over the new parinfer feature, maybe another request: I would like to “format and align” function for maps to also work in “vectors-containing-pairs”, for example the bindings of a let-block… Does that sound like a good idea?

Stefan14:11:03

@pez RE parinfer: I noticed that, given a file with incorrect indentation, when you edit it the brackets will be changed according to the indentation, which breaks the file. Because the indentation was wrong to begin with. I have parinfer also configured in vim, and there when I edit the same file, it will first correct the indentation before doing anything else, which solves the issue in a very nice way IMHO…

pez15:11:02

I didn’t know that parinfer broke the structure, maybe I am using the wrong options…