cql-rb 1.1.0.pre7 → 1.1.0.pre8

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    N2VjM2JjM2ZiNjU3MTkzOTk4MTU2MjUyMWViZWIwYTExMjc4MTQ0MA==
+    NzkxNmUwM2YwMzllNGEyNGU4NmY0Mjg1N2RmYzBmZjQ0NmU1ODE3NQ==
   data.tar.gz: !binary |-
-    OWQ2NWYxY2UwN2YxNjM0NmYxZmRlMmViMmI3OGJlMDdmZTE2NDY3Zg==
+    ZDJhMzk2Nzg1MGNiODYxNjYwYTcyY2YyMjcwZmRhYjU4OGMyY2MxYg==
 SHA512:
   metadata.gz: !binary |-
-    OTZkNmMzNjk5MDRhODdjZmNkMzljZDMxMzA2ZWQ1MWFjM2EyNWI3NmZmMjI2
-    OWZlMzY3NTczOTZiYzY2YmQ2ZWFmZWQ0ZTM1M2NjODBkOTI0MzMwODc2YmEx
-    OTBhNzdiZWNjYWY0YzA4NTQyNzc2NThhNTY2ZWM1ZDFmYmRjMDg=
+    MTBmMzM1NzYyYTk3ODc0YjgyMzE1ODA0ZWE4ODVkMzc3ZjQ0ODE0YTY3MjA0
+    MzRiODU5OGFlMjEzYmZkYTQ2MzI3MmFiMDQxYWNiOTI0NjMzYjQ1YjdlNjE4
+    NDlmNjJjZTI0NjJiMGIyMjhhNzNjYzc0N2JkZmEyNzhkZDViM2E=
   data.tar.gz: !binary |-
-    NGM4NmMyZDRhOTE3MTg4NmNjOGFmYmZhNmU5MWRiMTkzOWM4NzhlYzE2YTRk
-    ZGFmODJmMGNiMGRlNjFmZTNhMTZhYjdmYzhmOTMwNmQwOWFjMDc5NTk5Y2Jj
-    OTRiYWVkMWY2ZTYxMzUxMmRiODY4ZGQ5MzE3NWRkYzk5MTVlMGU=
+    NWFmNzk3MTc2NzlmOWJhZDlkMDAwYmNjNGNmNDUwN2Q0M2Y2NmEzNTZjY2Fi
+    NjIxMzQ2MjYxMTZiN2NhMzc1Y2M4ODg3MDdjYjQ3MmVjZGEwMDZlOGEwMjY5
+    YTc1YWZjOGU0MzVjOTcwZDIzMTc4OTE4ZDc1N2ZkODk4YjU4MmI=

data/README.md

@@ -151,13 +151,13 @@ Read more about CQL3 in the [CQL3 syntax documentation](https://github.com/apach
 
 ## I get "Deadlock detected" errors
 
-This means that the driver's IO reactor has crashed hard. Most of the time it means that you're using a framework, server or runtime that forks and you call `Client.connect` in the parent process. Check the documentation and see if there's any way you can register to run some piece of code in the child process just after a fork.
+This means that the driver's IO reactor has crashed hard. Most of the time it means that you're using a framework, server or runtime that forks and you call `Client.connect` in the parent process. Check the documentation and see if there's any way you can register to run some piece of code in the child process just after a fork, and connect there.
 
 This is how you do it in Resque:
 
 ```ruby
 Resque.after_fork = proc do
-  # ...
+  # connect to Cassandra here
 end
 ```
 
@@ -166,7 +166,7 @@ and this is how you do it in Passenger:
 ```ruby
 PhusionPassenger.on_event(:starting_worker_process) do |forked|
   if forked
-    # ...
+    # connect to Cassandra here
   end
 end
 ```
@@ -175,7 +175,7 @@ in Unicorn you do it in the config file:
 
 ```ruby
 after_fork do |server, worker|
-  # ...
+  # connect to Cassandra here
 end
 ```
 
@@ -199,7 +199,7 @@ Port 9160 is the old Thrift interface, the binary protocol runs on 9042. This is
 
 ## One of my Cassandra nodes crashed, and my application crashed, isn't Cassandra supposed to be fault tolerant?
 
-Yes it is, and your data is probably safe. cql-rb is just not completely there yet. Ideally it should handle connectivity issues and just talk to the nodes it can talk to and reconnect when things get back to normal. It's on the roadmap.
+Yes it is, and your data is probably safe. cql-rb is just not completely there yet. Ideally it should handle connectivity issues and just talk to the nodes it can talk to and reconnect when things get back to normal. _This is fixed in HEAD and will be released with v1.1.0_.
 
 ## Something else is not working
 
@@ -212,8 +212,8 @@ Check out the [releases on GitHub](https://github.com/iconara/cql-rb/releases).
 # Known bugs & limitations
 
 * No automatic peer discovery -- _this is in HEAD and will be released with v1.1.0_.
-* No automatic reconnection on connection failures -- _this is planned for v1.1.0_.
-* No support for request timeouts (other than server-initiated), but requests to a node fail when that node goes down.
+* No automatic reconnection on connection failures -- _this is in HEAD and will be released with v1.1.0_.
+* No support for request timeouts (other than server-initiated), but requests to a node fail when that node goes down -- _this is in HEAD and will be released with v1.1.0_.
 * No support for compression.
 * No support for request tracing.
 * JRuby 1.6.8 and earlier is not supported, the tests pass in 1.6.8, but 1.6.4 is known not to work. Travis does not support JRuby 1.6.x so there's no way to get good coverage of what works and not. The only known issue in 1.6.8 is that connection failures aren't handled correctly.

data/lib/cql/future.rb

@@ -327,18 +327,21 @@ module Cql
     #
     # @return [Object] the value of this future
     def value
+      semaphore = nil
       @lock.synchronize do
         raise @error if @failed
         return @value if @resolved
-        t = Thread.current
-        u = proc { t.run }
+        semaphore = Queue.new
+        u = proc { semaphore << :unblock }
         @value_listeners << u
         @failure_listeners << u
-        while true
+      end
+      while true
+        @lock.synchronize do
           raise @error if @failed
           return @value if @resolved
-          @lock.sleep
         end
+        semaphore.pop
       end
     end
 

data/lib/cql/version.rb

@@ -1,5 +1,5 @@
 # encoding: utf-8
 
 module Cql
-  VERSION = '1.1.0.pre7'.freeze
+  VERSION = '1.1.0.pre8'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cql-rb
 version: !ruby/object:Gem::Version
-  version: 1.1.0.pre7
+  version: 1.1.0.pre8
 platform: ruby
 authors:
 - Theo Hultberg
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-07 00:00:00.000000000 Z
+date: 2013-10-14 00:00:00.000000000 Z
 dependencies: []
 description: A pure Ruby CQL3 driver for Cassandra
 email: