https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112016-02-22T17:25:35ZRuby Issue Tracking SystemRuby master - Feature #12101: Add verbose failure messages and avoid infamous DRb::DRbConnErrorhttps://bugs.ruby-lang.org/issues/12101?journal_id=570822016-02-22T17:25:35Zyagudaev (Michael Yagudaev)
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li></ul> Ruby master - Feature #12101: Add verbose failure messages and avoid infamous DRb::DRbConnErrorhttps://bugs.ruby-lang.org/issues/12101?journal_id=570832016-02-22T18:30:11Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul></ul><p>I think printing out messages to $stdout is not the best way. If I'm running DRb as a server I may have no way of seeing these and knowing if it is a problem.</p>
<p>Better, I think, would be to allow a user to configure a callback or logger that is invoked when an error on the client side is discovered.</p>
<p>See also <a href="https://rubygems.org/gems/drbdump" class="external">https://rubygems.org/gems/drbdump</a> which gives you tcpdump-like views of communications amongst drb peers.</p> Ruby master - Feature #12101: Add verbose failure messages and avoid infamous DRb::DRbConnErrorhttps://bugs.ruby-lang.org/issues/12101?journal_id=571892016-02-28T11:28:11Zseki (Masatoshi Seki)seki@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Applied in changeset r53962.</p>
<hr>
<ul>
<li>lib/drb/drb.rb (error_print): Add verbose failure messages and<br>
avoid infamous DRb::DRbConnError. [Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add verbose failure messages and avoid infamous DRb::DRbConnError (Closed)" href="https://bugs.ruby-lang.org/issues/12101">#12101</a>]</li>
</ul>