Fork me on GitHub
#calva
<
2024-04-22
>
Eugen08:04:40

hi, I have a compilation failure because of a missing class and I don't know which part of the code is causing it. Isn't Calva supposed to show the full stack trace or the line that caused the compilation failure? Context: Trying to work out a project with ring-adapter with jetty 11

; Evaluating file: main.clj
;
; ; clj  snm.main
; Execution error (ClassNotFoundException) at jdk.internal.loader.BuiltinClassLoader/loadClass (BuiltinClassLoader.java:641).
; org.eclipse.jetty.util.Attributes
; Evaluation of file main.clj failed: class clojure.lang.Compiler$CompilerException

pez08:04:32

I think we don’t give access to the stack trace when loading the file. Evaluating the ns form should, though. It’ll be a small button below the error message.

Eugen08:04:33

I did not manage to do that. I looked for a command to evaluate ns = could not find it. I positioned cursor after ns parens and evaluated current form - that did not work either - same error. no stack trace

pez08:04:55

It was positioning the cursor by the form and evaluating it that I was suggesting. You should get a small button Show stacktrace, I don’t understand why you don’t get that. But there’s also a command for it. See if that works.

pez08:04:11

But you don’t need Calva for it. Evaluating *e after getting the error message works too. Calva’s stacktrace is basically the same, just a bit curated.

Eugen08:04:45

thanks Peter, noting seems to work for me today - I am going to take a break

pez08:04:52

I get this in the inspector after evaluating *e

Eugen09:04:45

yes, evaluating the *e symbol works fine. thanks

🙏 2
Eugen09:04:55

I made a repro for a ring-issue, thanks

pez09:04:40

You mean the Calva command for printing the stacktrace didn’t work? If so, I’d like a repro of that. 😃

Eugen09:04:14

I would like to know how to make one - but I don't at this point