que 0.11.1 → 0.11.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d5b079fcd58e807e529a24355cd68b1f01872824
-  data.tar.gz: 28e4205134326cdcd0a9f0416d96796dfeecfb99
+  metadata.gz: 20a82205491645e72a518cdf75314214732d7592
+  data.tar.gz: 35abbe3fbb3f8b8f43dcc3fb5c62eeb09fd2de36
 SHA512:
-  metadata.gz: 42b58920c74ab27e09647987ede2ae07a362c034b557d1fcbea21cfdcaf8ae64eb712d4688731bfab10bd7ebbb28c384dc5c431a6854245852e8a2a491b9e626
-  data.tar.gz: ab299f61a338f3ae5b26cf3186beda5c15313e0fce0da6287676fc4faa6e0a7d0ec896376f9fdfb44f9e4e4aa3bdf6f06b46417ed81a12a55d8493597cf5a261
+  metadata.gz: 21344fb8e7a6e0548cef67e9c8b27e439deb13588b9e94d2d0575ca63f8c5999f11960d2e81de5813f5208fd7fe39c364919bc0f41742470ab7a83466f1d3197
+  data.tar.gz: d93fda616f7efb5d05d7c02352aa0c3dab32dcb525400854b706827d977ccca7d61d5f2052ac046872540b98917f3f78e5baddded650c99c735cb2b3c8faecc3

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+### 0.11.2 (2015-09-09)
+
+*   Fix Job class constantizing when ActiveSupport isn't loaded. (#121) (godfat)
+
 ### 0.11.1 (2015-09-04)
 
 *   The `rake que:work` rake task that was specific to Rails has been deprecated and will be removed in Que 1.0. A deprecation warning will display when it is run.

data/README.md

@@ -129,10 +129,10 @@ Regarding contributions, one of the project's priorities is to keep Que as simpl
 
 A note on running specs - Que's worker system is multithreaded and therefore prone to race conditions (especially on interpreters without a global lock, like Rubinius or JRuby). As such, if you've touched that code, a single spec run passing isn't a guarantee that any changes you've made haven't introduced bugs. One thing I like to do before pushing changes is rerun the specs many times and watching for hangs. You can do this from the command line with something like:
 
-    for i in {1..1000}; do rspec -b --seed $i; done
+    for i in {1..1000}; do bundle exec rspec -b --seed $i; done
 
 This will iterate the specs one thousand times, each with a different ordering. If the specs hang, note what the seed number was on that iteration. For example, if the previous specs finished with a "Randomized with seed 328", you know that there's a hang with seed 329, and you can narrow it down to a specific spec with:
 
-    for i in {1..1000}; do LOG_SPEC=true rspec -b --seed 329; done
+    for i in {1..1000}; do LOG_SPEC=true bundle exec rspec -b --seed 329; done
 
 Note that we iterate because there's no guarantee that the hang would reappear with a single additional run, so we need to rerun the specs until it reappears. The LOG_SPEC parameter will output the name and file location of each spec before it is run, so you can easily tell which spec is hanging, and you can continue narrowing things down from there.

data/lib/que.rb

@@ -134,7 +134,7 @@ module Que
         # Use ActiveSupport's version if it exists.
         camel_cased_word.constantize
       else
-        string.split('::').inject(Object, &:const_get)
+        camel_cased_word.split('::').inject(Object, &:const_get)
       end
     end
 

data/lib/que/version.rb

@@ -1,3 +1,3 @@
 module Que
-  Version = '0.11.1'
+  Version = '0.11.2'
 end

data/spec/unit/work_spec.rb

@@ -1,5 +1,4 @@
 require 'spec_helper'
-require 'active_support/core_ext/date' # For the .seconds.from_now below
 
 describe Que::Job, '.work' do
   it "should pass a job's arguments to the run method and delete it from the database" do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: que
 version: !ruby/object:Gem::Version
-  version: 0.11.1
+  version: 0.11.2
 platform: ruby
 authors:
 - Chris Hanks
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-09-04 00:00:00.000000000 Z
+date: 2015-09-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler