olleolleolle[m] has quit [Quit: Idle for 30+ days]
jeremyevans has quit [Quit: Lost terminal]
<kalenp[m]>
I know that JRuby does some munging of backtraces to try to clean them up. Is that applied to arbitrary Throwables from Java, or just for exceptions thrown from Ruby land?
jeremyevans has joined #jruby
<headius[m]>
Just exceptions from Ruby land where we control the backtrace
<headius[m]>
We used to post process all exceptions from java calls but it added a lot of overhead to Java calls and often hid traces people needed to see
<kalenp[m]>
any way to opt into that for a particular Throwable?
<kalenp[m]>
I'm working on some error logging code and the stacks we're getting from java are pretty noisy with the raw jruby pieces in there
<headius[m]>
Hmm that is an interesting idea
<headius[m]>
There is nothing in place to have special logic for specific exception types but it could be something done at the method binding level, like you set a flag that says to process the backtrace
<headius[m]>
So short answer is no there is nothing like that now but there could be
<kalenp[m]>
alright, I'll just go with the java stack and squint at the noise. thanks for the quick reply!
nirvdrum has quit [Ping timeout: 240 seconds]
nirvdrum has joined #jruby
<headius[m]>
Might be worth opening an issue to add such a feature, I don't know exactly what it would look like but it has come up before
<headius[m]>
I have wondered about hooking into the jvm exception raising process more directly but unsure how that would work