hopper 0.0.1.pre.alpha.1 → 0.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 33d562bd6dd3fb4fbf879d90de308e9a065545ff
-  data.tar.gz: b9a8719f539441ef1a9d2807a1075f0ae1131844
+  metadata.gz: 27d2b14dd2167a64a19313222427ca9f1096074b
+  data.tar.gz: bbd8f806df0f11709081abb213ced5d4c1f7d3ae
 SHA512:
-  metadata.gz: 4d050bda365e3af3e77f0592b169e9e713e4fa5c7ce550b3c8e09fb8cb82461f67783ae47c689f78c6aba1d5c5389ebec6aae29c8cce4328268fc9c956052658
-  data.tar.gz: f1be57515a48a11bc67947c8bad4225d5fc4f44db0162d51e72ac567969265e43c46f824e4563622cafd872734098c76bd10e723665bf0d4de2a05b13d58e565
+  metadata.gz: a06a597fc6c1bd5eda7ce1dd7382604994c4493f5abdabfd008db9aa5501a1ba0fc2a2f256d761818888bc746a360c6685e9e23a3f69350c9962cfe755715aff
+  data.tar.gz: 1823412b728c4380f2fa366d4bbdf7813b9c569bfdeed9037feb8898eccbffcc8579238d21274cc7614d85d8a45458f247bd442cc8c774a8a3ab13eaa74758ae

data/CONTRIBUTING.md

@@ -0,0 +1,33 @@
+Contributing to Hopper
+======================
+
+First of all, thanks for your interest in contributing to Hopper!
+
+Below are a list of guidelines to help keep this project sane in the face of open source entropy.
+
+How To Submit A Patch
+---------------------
+
+Any patch you feel would make this a better project is welcome, including but not limited to: bug fixes, new features, refactoring, and better documentation.
+
+Make a fork of this project, and hack to your heart's content. Once you have something you think would be great to include into master, feel free to open a pull request. Please keep in mind the following guidelines, which will make it more likely for your pull request to be accepted:
+
+1. Please have test cases, both in the unit suite and the integration suite, that fail when your code is not present.
+1. Please open a topic branch in your fork, and create your pull request against that.
+ * Use a separate topic for each feature and/or bug fix you want to submit.
+1. Be logically consistent in your commits. Make them as small as possible, so they can tell a story the maintainer can understand.
+1. Keeping a consistent style in the codebase is important for maintainability. When possible, please stick to the guidelines within [this guide](https://github.com/bbatsov/ruby-style-guide).
+1. Pay attention to things like code climate and test coverage. A drop in these metrics will not necessarily preclude a patch from being accepted, but we'd much prefer to keep these numbers high.
+
+Please keep in mind your contributions will be licensed the same as the rest of Hopper, under the MIT license.
+
+It may take the developer a day or two to get to your pull request. If your request has not been responded to in a few days, though, feel free to ping the developer team, preferably through a comment on the pull.
+
+How To Report An Issue
+----------------------
+
+Issue reports are welcome, even if not accompanied by a pull request. Keep in mind that submitting a pull request will mean your issue likely gets resolved sooner, because less work will be left to do.
+
+The most important thing an issue can do is get a developer as close as possible to seeing what you are seeing, in the case of a bug report. In the case of a feature request, you want to get them to the point where they don't see what you want to see, so they can make a decision about whether and how to include the proposed feature. 
+
+More about good bug reports [here](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).

data/README.md

@@ -1,3 +1,71 @@
+[![Build Status](https://travis-ci.org/azanar/hopper.svg)](https://travis-ci.org/azanar/hopper)
+[![Dependency Status](http://img.shields.io/gemnasium/azanar/hopper.svg)](https://gemnasium.com/azanar/hopper)
+[![Coverage Status](http://img.shields.io/coveralls/azanar/hopper.svg)](https://coveralls.io/r/azanar/hopper)
+[![Code Climate](http://img.shields.io/codeclimate/github/azanar/hopper.svg)](https://codeclimate.com/github/azanar/hopper)
+[![Gem Version](http://img.shields.io/gem/v/hopper.svg)](https://rubygems.org/gems/hopper)
+[![License](http://img.shields.io/:license-mit-blue.svg)](http://azanar.mit-license.org)
+[![Badges](http://img.shields.io/:badges-7/7-ff6799.svg)](https://github.com/badges/badgerbadgerbadger)
+
+
 Hopper
 ======
 A framework for task execution written around bunny.
+
+Usable on its own, or as part of [Hopper](https://github.com/azanar/hopper).
+
+Examples
+--------
+A Publisher:
+
+```ruby
+  channel = Hopper::Channel.new
+
+  queue = Hopper::Queue.new("hopper-stresstest")
+
+  publisher = queue.publisher(channel)
+  
+  publisher.publish(m)
+```
+
+A Listener:
+```ruby
+ channel = Hopper::Channel.new
+
+ queue = Hopper::Queue.new("hopper-stresstest")
+  
+ listener = queue.listener(channel)
+
+ listener.listen do |m|
+          
+  unless valid(m)
+    m.reject
+    next
+  end
+  
+  # do some stuff
+  
+  m.acknowledge
+end
+```
+
+TODO
+----
+
+- Add support for pluggable serialization mechanisms (MsgPack, JSON, etc.)
+
+API Documentation
+-----------------
+
+See [RubyDoc](http://rubydoc.info/github/azanar/hopper/index)
+
+Contributors
+------------
+
+See [Contributing](CONTRIBUTING.md) for details.
+
+License
+-------
+
+©2015 Ed Carrel. Released under the MIT License.
+
+See [License](LICENSE) for details.

data/lib/hopper/version.rb

@@ -1,3 +1,3 @@
 module Hopper
-  VERSION = "0.0.1-alpha.1"
+  VERSION = "0.0.1"
 end

data/test/integration/hopper_test.rb

@@ -2,7 +2,7 @@ require File.expand_path('../test_helper', __FILE__)
 
 require 'bunny'
 
-require 'timeout'
+require 'thread'
 
 require 'hopper'
 
@@ -15,7 +15,7 @@ module Hopper
       channel = Hopper::Channel.new
 
       queue = Hopper::Queue.new("hopper-stresstest")
-    
+
       publisher = queue.publisher(channel)
       listener = queue.listener(channel)
 
@@ -26,36 +26,55 @@ module Hopper
       channel = Hopper::Channel.new
 
       queue = channel.queue("hopper-stresstest")
-    
+
       publisher = queue.publisher
       listener = queue.listener
-      
+
       run_queue(publisher, listener)
 
     end
 
+    QUEUE_LENGTH = 100
+
     def run_queue(publisher, listener)
-      messages = 10.times.map do |x|
-        Message.new("message#{x}")
+      message_strings = QUEUE_LENGTH.times.map do |x|
+        "message#{x}"
+      end
+
+      messages = message_strings.map do |s|
+        Message.new(s)
       end
-      
+
       messages.each do |m|
         publisher.publish(m)
       end
 
       received = []
 
-      Timeout::timeout(1) do
+      validate_mutex = Mutex.new
+      validate_latch = ConditionVariable.new
+
+      Thread.new do
         listener.listen do |m|
           received << m
           m.acknowledge
-          if received.length == 10
+          if received.length == QUEUE_LENGTH
+            validate_latch.signal
             m.terminate
           end
         end
       end
 
-      assert_equal 10, received.length
+      validate_mutex.synchronize {
+        validate_latch.wait(validate_mutex)
+      }
+
+      assert_equal QUEUE_LENGTH, received.length
+      received_strings = received.map {|r|
+        r.message.payload
+      }
+      assert_equal Set.new(message_strings), Set.new(received_strings)
     end
+
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hopper
 version: !ruby/object:Gem::Version
-  version: 0.0.1.pre.alpha.1
+  version: 0.0.1
 platform: ruby
 authors:
 - Ed Carrel
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-10-21 00:00:00.000000000 Z
+date: 2015-05-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -131,6 +131,7 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - ".travis.yml"
+- CONTRIBUTING.md
 - Gemfile
 - LICENSE
 - README.md
@@ -175,12 +176,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.5
 signing_key: 
 specification_version: 4
 summary: A framework for task execution written around bunny