-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Low-level Java error printed on Errno::EPIPE exception #5003
Comments
Errant printStackTrace() from 2004 O_o.
HAHAH that should have read 2014. Which was still impressively old but not EPIC |
@enebo Thank you for such a quick fix! |
@enebo I'm still seeing the same low-level Java error in JRuby 9.1.17.0 when I execute the script above. |
@janko-m I do not see this:
Is it possible there is an env like JRUBY_HOME or somehow the older jar is there? Also paste the new stacktrace/ The line numbers will definitely not be exactly the same; so if you see that then it is likely calling an older version still. |
Hmm, that's strange. Here is the stack trace:
I deleted the previous JRuby version with
I actually first noticed the output still being there in the Travis CI build output for |
@janko-m oh ffs :| yeah I committed this to our master branch and not out jruby-9.1 branch :( Sorry for a) not actually fixing it in the right place b) making you verify it is actually broken. |
Errant printStackTrace() from 2004 O_o.
No problem, thanks for pushing it out to the |
Environment
Expected Behavior
When writing to a broken pipe using
IO.copy_stream
, I expectErrno::EPIPE
exception to be raised without anything else printed, as it is the case on MRI:Actual Behavior
On JRuby, in addition to the
Errno::EPIPE
exception, we get ajava.io.IOException: Broken pipe
internal exception also printed out:Note that the behaviour is still the same, an
Errno::EPIPE
exception is still raised, but in addition to thatjava.io.IOException: Broken pipe
stack trace is displayed, even when I rescueErrno::EPIPE
. The thing is that in my case I'm expecting thatErrno::EPIPE
will be raised in certain scenarios, so this internal Java stack trace is something that I would prefer wasn't there, because no exception was actually raised.The text was updated successfully, but these errors were encountered: