From: seki@... Date: 2017-01-22T03:19:05+00:00 Subject: [ruby-core:79214] [Ruby trunk Bug#13127][Closed] DRb `load': connection closed (DRb::DRbConnError) when client exit's from within a loop iterating over remote objects Issue #13127 has been updated by Masatoshi Seki. Status changed from Assigned to Closed what's happen? ~~~ # S: drb_server_test.rb # C: drb_client_test.rb # (1) C send :each_with_index, &block to my_array in S. remote_object.each_with_index # (2) S send :yield to &block in C. do |obj, index| puts "#{obj.name}" if index > 5 exit (1) # exit() then failed (2), and generate backtrace. end end ~~~ Can you use Kernel.exit! instead of exit ? ---------------------------------------- Bug #13127: DRb `load': connection closed (DRb::DRbConnError) when client exit's from within a loop iterating over remote objects https://bugs.ruby-lang.org/issues/13127#change-62634 * Author: Madhu Kanoor * Status: Closed * Priority: Normal * Assignee: Masatoshi Seki * Target version: * ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Calling exit from a DRb client inside a do block while iterating over remote objects causes a DRb connection closed error. This error doesn't happen when working with local objects. To recreate the problem start the drb server using **ruby drb_server_test.rb** run the client **ruby drb_client_test.rb** The client code fails with a stack trace ---Files-------------------------------- drb_server_test.rb (282 Bytes) drb_client_test.rb (206 Bytes) output.txt (2.11 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: