que 0.9.0 → 0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6e9631191c30bd35b86706f09611faebc0f99e07
-  data.tar.gz: b53b3005e278471f4e4ee7e55a41637db002a2be
+  metadata.gz: 85eb4ac59563d5e8ca4a6ca6941646b17d747d66
+  data.tar.gz: b028b1087c1b8821e729184aef18be61d7b0f276
 SHA512:
-  metadata.gz: 7a8da4e60a2d3e9bd85be9891cf7d3c736621ed5e72d07d2f6145e2430ca7af15d678441c2d3bd9358aee1aab84fde5a73d14be0af1a87c2425a3ec51de652de
-  data.tar.gz: 1245796b0d471b8ab3ccc528f016cb244dad07fc80282fcae82e5bd1203281df01e40bd012e04cc1eade1a63a8424a3488043a81ddf68d02886ca6b8256c5067
+  metadata.gz: 324b8119b2b5ab4ee7653318aff68667f25ae835feb2928bc1ae522dacbe71f3cb6c493f1014417c25f7565b4fd6594edeeda66c8db7452f285c72226768803a
+  data.tar.gz: f3030170abe60c4da26a155743632b978f224de283d24b071b8ade4232cc8958d1dd9cbef86fbac1aa28682ba3feda8589aabf3a2c7ec4e59a35aec7718d71b8

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+### 0.9.1 (2015-01-11)
+
+*   Use now() rather than 'now' when inserting jobs, to avoid using an old value as the default run_at in prepared statements. (#74) (bgentry)
+
 ### 0.9.0 (2014-12-16)
 
 *   The error_handler callable is now be passed two objects, the error and the job that raised it. If your current error_handler is a proc, as recommended in the docs, you shouldn't need to make any code changes, unless you want to use the job in your error handling. If your error_handler is a lambda, or another callable with a strict arity requirement, you'll want to change it before upgrading. (#69) (statianzo)

data/README.md

@@ -96,20 +96,21 @@ You can also add options to run the job after a specific time, or with a specifi
 ChargeCreditCard.enqueue current_user.id, :credit_card_id => card.id, :run_at => 1.day.from_now, :priority => 5
 ```
 
-To determine what happens when a job is queued, you can set Que's mode in your application configuration. There are a few options for the mode:
+To determine what happens when a job is queued, you can set Que's mode. There are a few options for the mode:
 
-  * `config.que.mode = :off` - In this mode, queueing a job will simply insert it into the database - the current process will make no effort to run it. You should use this if you want to use a dedicated process to work tasks (there's a rake task to do this, see below). This is the default when running `bin/rails console`.
-  * `config.que.mode = :async` - In this mode, a pool of background workers is spun up, each running in their own thread. This is the default when running `bin/rails server`. See the docs for [more information on managing workers](https://github.com/chanks/que/blob/master/docs/managing_workers.md).
-  * `config.que.mode = :sync` - In this mode, any jobs you queue will be run in the same thread, synchronously (that is, `MyJob.enqueue` runs the job and won't return until it's completed). This makes your application's behavior easier to test, so it's the default in the test environment.
+  * `Que.mode = :off` - In this mode, queueing a job will simply insert it into the database - the current process will make no effort to run it. You should use this if you want to use a dedicated process to work tasks (there's a rake task to do this, see below). This is the default when running `bin/rails console`.
+  * `Que.mode = :async` - In this mode, a pool of background workers is spun up, each running in their own thread. This is the default when running `bin/rails server`. See the docs for [more information on managing workers](https://github.com/chanks/que/blob/master/docs/managing_workers.md).
+  * `Que.mode = :sync` - In this mode, any jobs you queue will be run in the same thread, synchronously (that is, `MyJob.enqueue` runs the job and won't return until it's completed). This makes your application's behavior easier to test, so it's the default in the test environment.
 
 If you're using ActiveRecord to dump your database's schema, you'll probably want to [set schema_format to :sql](http://guides.rubyonrails.org/migrations.html#types-of-schema-dumps) so that Que's table structure is managed correctly.
 
-## Related Gems
+## Related Projects
 
   * [que-web](https://github.com/statianzo/que-web) is a Sinatra-based UI for inspecting your job queue.
   * [que-testing](https://github.com/statianzo/que-testing) allows making assertions on enqueued jobs.
+  * [que-go](https://github.com/bgentry/que-go) is a port of Que for the Go programming language. It uses the same table structure, so that you can use the same job queue from Ruby and Go applications.
 
-If you have a gem that uses or relates to Que, feel free to submit a PR adding it to the list!
+If you have a project that uses or relates to Que, feel free to submit a PR adding it to the list!
 
 ## Contributing
 

data/docs/error_handling.md

@@ -23,7 +23,3 @@ If you're using an error notification system (highly recommended, of course), yo
     Que.error_handler = proc do |error|
       # Do whatever you want with the error object.
     end
-
-    # Or, in your Rails configuration:
-
-    config.que.error_handler = proc { |error| ... }

data/docs/logging.md

@@ -8,10 +8,6 @@ Of course you can have it log wherever you like:
 
     Que.logger = Logger.new(...)
 
-    # Or, in your Rails configuration:
-
-    config.que.logger = Logger.new(...)
-
 You can use Que's logger in your jobs anywhere you like:
 
     class MyJob

data/docs/managing_workers.md

@@ -12,9 +12,6 @@ You can change the number of workers in the pool whenever you like by setting th
 
     Que.worker_count = 8
 
-    # Or, in your Rails configuration:
-    config.que.worker_count = 8
-
 ### Working Jobs Via Rake Task
 
 If you don't want to burden your web processes with too much work and want to run workers in a background process instead, similar to how most other queues work, you can:
@@ -35,9 +32,6 @@ If your application code is not thread-safe, you won't want any workers to be pr
 
     Que.mode = :off
 
-    # Or, in your Rails configuration:
-    config.que.mode = :off
-
 This will prevent Que from trying to process jobs in the background of your web processes. In order to actually work jobs, you'll want to run a single worker at a time, and to do so via a separate rake task, like so:
 
     QUE_WORKER_COUNT=1 rake que:work
@@ -46,10 +40,7 @@ This will prevent Que from trying to process jobs in the background of your web
 
 If a worker checks the job queue and finds no jobs ready for it to work, it will fall asleep. In order to make sure that newly-available jobs don't go unworked, a worker is awoken every so often to check for available work. By default, this happens every five seconds, but you can make it happen more or less often by setting a custom wake_interval:
 
-    Que.wake_interval = 2
-
-    # Or, in your Rails configuration:
-    config.que.wake_interval = 2   # 2.seconds also works fine.
+    Que.wake_interval = 2 # In Rails, 2.seconds also works fine.
 
 You can also choose to never let workers wake up on their own:
 

data/lib/que/sql.rb

@@ -60,7 +60,7 @@ module Que
       INSERT INTO que_jobs
       (queue, priority, run_at, job_class, args)
       VALUES
-      (coalesce($1, '')::text, coalesce($2, 100)::smallint, coalesce($3, 'now')::timestamptz, $4::text, coalesce($5, '[]')::json)
+      (coalesce($1, '')::text, coalesce($2, 100)::smallint, coalesce($3, now())::timestamptz, $4::text, coalesce($5, '[]')::json)
       RETURNING *
     }.freeze,
 

data/lib/que/version.rb

@@ -1,3 +1,3 @@
 module Que
-  Version = '0.9.0'
+  Version = '0.9.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: que
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
 platform: ruby
 authors:
 - Chris Hanks
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-12-16 00:00:00.000000000 Z
+date: 2015-01-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler