Besides #2106 where a Ruby exception was raised and a Java stack trace dumped to stdout/err there seems to be cases when Java exceptions are not handled and are delivered to the Ruby code:
Ahh, good, this I can deal with. We have logic that turns IOException into the appropriate kind of Ruby error, but because Java only gives us a string message to indicate what happened we have some gaps in the translation. Will investigate.
Besides #2106 where a Ruby exception was raised and a Java stack trace dumped to stdout/err there seems to be cases when Java exceptions are not handled and are delivered to the Ruby code:
The full stack traces are here: https://gist.github.com/iconara/95642ed9ce8ff2aaa98b#file-output2
Here's the first few lines:
The text was updated successfully, but these errors were encountered: