You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The linked patch to clojure condenses the stack trace to the important line(s). It would be great to see something similar for ring.
Important lines would be the cause and the lines for files in the current app (handler.clj:116 my-app.handler/a-function)
To me this is the most important for the sterr logging. When the error is displayed in the browser, it seems fine to show the whole trace. In the browser it looks like there is some attempt to style less important line with a lighter font. This could be a little easier to read if the same important line(s) were highlighted.
The text was updated successfully, but these errors were encountered:
sirmspencer
changed the title
[stacktrace.clj] Allow condensed stack trace format to match clojure 1.10.1 update
[stacktrace.clj] Allow condensed stack trace format
Jan 28, 2020
I see that errors are also returned with a :trimmed-elems that is the shorter trace. This is a good key to use instead of trying to filter elems based on file or something else.
https://clojure.atlassian.net/browse/CLJ-2463
The linked patch to clojure condenses the stack trace to the important line(s). It would be great to see something similar for ring.
Important lines would be the cause and the lines for files in the current app (handler.clj:116 my-app.handler/a-function)
To me this is the most important for the sterr logging. When the error is displayed in the browser, it seems fine to show the whole trace. In the browser it looks like there is some attempt to style less important line with a lighter font. This could be a little easier to read if the same important line(s) were highlighted.
The text was updated successfully, but these errors were encountered: