Bug #8125


lost-tuple bug and fix for Rinda::TupleSpaceProxy.take

Added by vjoel (Joel VanderWerf) about 10 years ago. Updated about 10 years ago.

Target version:
ruby -v:
ruby 2.0.0p0 (2013-02-24) [x86_64-linux]



Rinda::TupleSpaceProxy prevents tuple loss during #take by exposing a "port" object on the client that the remote side (the tuplespace server) pushes to, instead of relying on the method return value. Pushing to the port fails if the process that called #take has exited, so the tuple will not be deleted from the tuplespace server.

However, if the process has not exited, and the thread that called #take was interrupted, the port still exists and accepts push requests (in the main drb thread). In this case the tuple is deleted on the server and not available on the client.

This is frequently a problem when using irb and manually interrupting take calls. It would also be a problem when using timeouts.

A concise reproduction of the problem is in the attached thread-int.rb.

The bug can be fixed by the patch below, which replaces the port array with a custom object that rejects pushes if the call stack has been unwound.

Note that this patch combines naturally with the faster take patch in #8119.

diff --git a/lib/rinda/rinda.rb b/lib/rinda/rinda.rb
index 18e284a..057c61a 100644
--- a/lib/rinda/rinda.rb
+++ b/lib/rinda/rinda.rb
@@ -206,6 +206,23 @@ module Rinda
# TupleSpaceProxy allows a remote Tuplespace to appear as local.

 class TupleSpaceProxy
  • class Port

  •  attr_reader :val
  •  def initialize
  •    @open = true
  •  end
  •  def close
  •    @open = false
  •  end
  •  def push val
  •    raise unless @open
  •    @val = val
  •    nil # so that val doesn't get marshalled again
  •  end
  • end

    Creates a new TupleSpaceProxy to wrap +ts+.

@@ -222,6 +239,19 @@ module Rinda

  • Safely takes +tuple+ from the proxied TupleSpace. See TupleSpace#take.

  • Ensures that an interrupted thread will not become a lasting cause

  • of further data loss.

  • def take_safely(tuple, sec=nil, &block)

  •  port =
  •  @ts.move(, tuple, sec, &block)
  •  port.val
  • ensure

  •  port.close # don't let the DRb thread push to it when remote sends tuple
  • end

  • Takes +tuple+ from the proxied TupleSpace. See TupleSpace#take.

    def take(tuple, sec=nil, &block)



thread-int.rb (1.1 KB) thread-int.rb vjoel (Joel VanderWerf), 03/20/2013 02:21 AM
rinda.rb.8215.patch (2.84 KB) rinda.rb.8215.patch drbrain (Eric Hodel), 03/23/2013 04:21 PM
rinda.rb.8215.2.patch (2.84 KB) rinda.rb.8215.2.patch drbrain (Eric Hodel), 03/23/2013 04:26 PM
rinda.rb.8215.3.patch (2.91 KB) rinda.rb.8215.3.patch drbrain (Eric Hodel), 03/23/2013 04:37 PM

Updated by hsbt (Hiroshi SHIBATA) about 10 years ago

  • Assignee set to seki (Masatoshi Seki)

Updated by drbrain (Eric Hodel) about 10 years ago

I think the safe take should be the default take.

I updated your patch and converted thread-int.rb into a test.

Updated by drbrain (Eric Hodel) about 10 years ago

Here is an updated patch that matches the rinda style and removes a leftover p

Updated by drbrain (Eric Hodel) about 10 years ago

Oops, I forgot to run all the tests, this fixes the remaining tests by restoring an accidentally deleted line.

Updated by seki (Masatoshi Seki) about 10 years ago

  • Assignee changed from seki (Masatoshi Seki) to drbrain (Eric Hodel)

please commit it!

Actions #6

Updated by drbrain (Eric Hodel) about 10 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r39890.
Joel, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

  • lib/rinda/rinda.rb: Fixed loss of tuple when remote is alive but the
    call stack was unwound. Patch by Joel VanderWerf.
    [ruby-trunk - Bug #8125]
    • test/rinda/test_rinda.rb: Test for the above.

Also available in: Atom PDF