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
Don't you think we should figure out why this was nil? My code was bad, causing an IndexOutOfBoundsException. In my eyes we just kicked the can down the road and now have another problem: a stacktrace buffer with no way to jump to the error location.
Maybe. I saw there was already some special handling in cider-stacktrace-render-cause for the case when message is nil, so I assumed it was a known scenario.
We can leave this issue open as a question of “Why didn't this stacktrace have a message?”
My guess would be: “Because the thrown exception was created without one”. I.e., (Exception.)
The text was updated successfully, but these errors were encountered: