que 1.0.0.beta5 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 90ae5c7c65d93f4ea3833d80351c2e0d3ed3f706ba00411937e8aba2137a41d7
-  data.tar.gz: 58aba934ee2735522e602dd5777de666c6acbee1cb531d9918ce6f2b75f3b693
+  metadata.gz: 967eded27a81df945b65911275dcdc7925113727bfd06fbc42cb780a3bfb6fcf
+  data.tar.gz: 87607b262263b13623b4b09822a478c02179e57cfa503f253e3e678ac8b1490a
 SHA512:
-  metadata.gz: 1cbfa5f3c6d13868897ac9f1fcf079aaeaa29c9eadfd231044a484878fbf8e99f4b159a4458690027b181b29c5da3abafcc1c9de2d33b3c487b1fac4a15c7e50
-  data.tar.gz: 1ed4b71f51cd72e3968de6ec745e2de592dc021e9d334526630b3011d3f5526388b8562da4bf513066cb68d4dee033043115027ddfc0e9bef5e816ed2c35ede5
+  metadata.gz: 3d8242fe07445a6f4658f322dd1a7cdb8918c8a56c2bfad2db49c58695b4ebae183e6a56159abc4ff74316006e7d95459ab6cfd8a4c98410eea50a2e4fb52509
+  data.tar.gz: 24fdf63cab7ff6e8a2ffa6ed598718d3c2ae2cbc6ef61de22ab6f1541b0cc23bab980fe5d10bbcb54823b2a529cd1cdc9d57437db3905e802bec92a04ea3ed94

data/CHANGELOG.md

@@ -1,3 +1,71 @@
+### 1.2.0 (2022-02-23)
+
+- **Deprecated**
+    + Providing job options as top level keyword arguments to Job.enqueue is now deprecated. Support will be dropped in `2.0`. Job options should be nested under the `job_options` keyword arg instead. See [#336](https://github.com/que-rb/que/pull/336)
+
+### 1.1.0 (2022-02-21)
+
+- **Features**:
+    + Add backtrace to errors, by [@trammel](https://github.com/trammel) in [#328](https://github.com/que-rb/que/pull/328)
+- **Internal**:
+    + Add Dockerised development environment, in [#324](https://github.com/que-rb/que/pull/324)
+
+### 1.0.0 (2022-01-24)
+
+_This release does not add any changes on top of 1.0.0.beta5._
+
+### 1.0.0.beta5 (2021-12-23)
+
+* **Bug fixes and improvements**
+    * Add more context to error message when config files fail to load. by [@trammel](https://github.com/trammel) in [#293](https://github.com/que-rb/que/pull/293)
+    * Fix lock leak on PostgreSQL 12 and later by [@jasoncodes](https://github.com/jasoncodes) in [#298](https://github.com/que-rb/que/pull/298)
+    * Fix deadlock issue [#318](https://github.com/que-rb/que/pull/318)
+    * Fix thread attrition issue [#321](https://github.com/que-rb/que/pull/321)
+
+* **Rails fixes:**
+    * Set schema in table_name for ActiveRecord model by [@nikitug](https://github.com/nikitug) in [#274](https://github.com/que-rb/que/pull/274)
+
+* **Documentation:**
+    * Add link to que-locks for exclusive job locking by [@airhorns](https://github.com/airhorns) in [#263](https://github.com/que-rb/que/pull/263)
+    [`5259303`](https://github.com/que-rb/que/commit/52593031a7eef2d52ac38eceb2d8df776ec74090)
+    * Fix links to Writing Reliable Jobs by [@nikitug](https://github.com/nikitug) in [#273](https://github.com/que-rb/que/pull/273)
+    * Add build badge to README by [@jonathanhefner](https://github.com/jonathanhefner) in [#278](https://github.com/que-rb/que/pull/278)
+    * Fix ToC links in docs by [@swrobel](https://github.com/swrobel) in [#287](https://github.com/que-rb/que/pull/287)
+    * Note all Rails queue names that must be changed by [@swrobel](https://github.com/swrobel) in [#296](https://github.com/que-rb/que/pull/296)
+    * Add instructions for how to start Que by [@xcskier56](https://github.com/xcskier56) in [#292](https://github.com/que-rb/que/pull/292)
+
+* **CI/tests**
+    * Fix CI failure from Docker Postgres image by [@jonathanhefner](https://github.com/jonathanhefner) in [#275](https://github.com/que-rb/que/pull/275)
+    * Test with Ruby 2.7 by [@jonathanhefner](https://github.com/jonathanhefner) in [#276](https://github.com/que-rb/que/pull/276)
+    * Run GitHub build workflow on push by [@jonathanhefner](https://github.com/jonathanhefner) in [#277](https://github.com/que-rb/que/pull/277)
+
+
+**Full Changelog**: [`v1.0.0.beta4...v1.0.0.beta5`](https://github.com/que-rb/que/compare/v1.0.0.beta4...v1.0.0.beta5)
+
+**Unless an issue is found we intend for this release to become v1.0.0 proper.**
+
+---
+
+### 1.0.0.beta4 (2020-01-17)
+
+- Rails 6 compatibility: Fix time parsing #249 and https://github.com/que-rb/que/commit/5ddddd5ebac6153d7a683ef08c86bced8e03fb51
+- Cleaner sequel usage #257
+- Documentation improvements #264 #269 #261 #231
+
+---
+
+### 1.0.0.beta3 (2018-05-18)
+
+*   Added support for customizing log levels for `job_worked` events (#217).
+
+*   Began logging all `job_errored` events at the `ERROR` log level.
+
+*   Fixed the Railtie when running in test mode (#214).
+
+*   Tweaked the meanings of worker-priorities and worker-count options in the CLI, to better support use cases with low worker counts (#216).
+
+---
+
 ### 1.0.0.beta2 (2018-04-13)
 
 *   **A schema upgrade to version 4 will be required for this release.** See [the migration doc](https://github.com/que-rb/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
@@ -111,8 +179,123 @@
     *   Names for queues and job classes are now limited to 500 characters, which is still far longer than either of these values should reasonably be.
 
     *   There is now a `data` JSONB column which is used to support various ways of organizing jobs (setting tags on them, etc).
+---
+
+### 1.0.0.beta (2017-10-25)
+
+*   **A schema upgrade to version 4 will be required for this release.** See [the migration doc](https://github.com/que-rb/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
+
+    *   Please note that this migration requires a rewrite of the jobs table, which makes it O(n) with the size of the table. If you have a very large backlog of jobs you may want to schedule downtime for this migration.
+
+*   Que's implementation has been changed from one in which worker threads hold their own PG connections and lock their own jobs to one in which a single thread (and PG connection) locks jobs through LISTEN/NOTIFY and batch polling, and passes jobs along to worker threads. This has many benefits, including:
+
+    *   Jobs queued for immediate processing can be actively distributed to workers with LISTEN/NOTIFY, which is more efficient than having workers repeatedly poll for new jobs.
+
+    *   When polling is necessary (to pick up jobs that are scheduled for the future or that need to be retried due to errors), jobs can be locked and fetched in batches, rather than one at a time.
+
+    *   Individual workers no longer need to monopolize their own (usually idle) connections while working jobs, so Ruby processes will require fewer Postgres connections.
+
+    *   PgBouncer or another external connection pool can be used for workers' connections (though not for the connection used to lock and listen for jobs).
+
+*   Other features introduced in this version include:
+
+    *   Much better support for all versions of ActiveJob.
 
-For a detailed list of the changes between each beta release of 1.0.0, see [the beta Changelog](CHANGELOG.1.0.beta.md).
+        *   In particular, you may (optionally) include `Que::ActiveJob::JobExtensions` into `ApplicationJob` to get support for all of Que's job helper methods.
+
+    *   Custom middleware that wrap running jobs are now supported.
+
+    *   Support for categorizing jobs with tags.
+
+    *   Support for configuring a `maximum_retry_count` on individual job classes.
+
+    *   Job configuration options are now inheritable, so job class hierarchies are more useful.
+
+    *   There are now built-in models for ActiveRecord and Sequel to allow inspecting the queue easily.
+
+    *   Jobs that have finished working may optionally be retained in the database indefinitely.
+
+        *   To keep a job record, replace the `destroy` calls in your jobs with `finish`. `destroy` will still delete records entirely, for jobs that you don't want to keep.
+
+        *   If you don't resolve a job yourself one way or another, Que will still `destroy` the job for you by default.
+
+        *   Finished jobs have a timestamp set in the finished_at column.
+
+    *   Jobs that have errored too many times will now be marked as expired, and won't be retried again.
+
+        *   You can configure a maximum_retry_count in your job classes, to set the threshold at which a job will be marked expired. The default is 15.
+
+        *   To manually mark a job as expired (and keep it in the database but not try to run it again) you can call `expire` helper in your job.
+
+    *   You can now set job priority thresholds for individual workers, to ensure that there will always be space available for high-priority jobs.
+
+    *   `Que.job_states` returns a list of locked jobs and the hostname/pid of the Ruby processes that have locked them.
+
+    *   `Que.connection_proc=` has been added, to allow for the easy integration of custom connection pools.
+
+*   In keeping with semantic versioning, the major version is being bumped since the new implementation requires some backwards-incompatible changes. These changes include:
+
+    *   Support for MRI Rubies before 2.2 has been dropped.
+
+    *   Support for Postgres versions before 9.5 has been dropped (JSONB and upsert support is required).
+
+    *   JRuby support has been dropped. It will be reintroduced whenever the jruby-pg gem is production-ready.
+
+    *   The `que:work` rake task has been removed. Use the `que` executable instead.
+
+        *   Therefore, configuring workers using QUE_* environment variables is no longer supported. Please pass the appropriate options to the `que` executable instead.
+
+    *   The `mode` setter has been removed.
+
+        *   To run jobs synchronously when they are enqueued (the old `:sync` behavior) you can set `Que.run_synchronously = true`.
+
+        *   To start up the worker pool (the old :async behavior) you should use the `que` executable to start up a worker process. There's no longer a supported API for running workers outside of the `que` executable.
+
+    *   The following methods are not meaningful under the new implementation and have been removed:
+
+        *   The `Que.wake_interval` getter and setter.
+
+        *   The `Que.worker_count` getter and setter.
+
+        *   `Que.wake!`
+
+        *   `Que.wake_all!`
+
+    *   Since Que needs a dedicated Postgres connection to manage job locks, running Que through a single PG connection is no longer supported.
+
+        *   It's not clear that anyone ever actually did this.
+
+    *   `Que.worker_states` has been removed, as the connection that locks a job is no longer the one that the job is using to run. Its functionality has been partially replaced with `Que.job_states`.
+
+    *   When using Rails, for simplicity, job attributes and keys in argument hashes are now converted to symbols when retrieved from the database, rather than being converted to instances of HashWithIndifferentAccess.
+
+    *   Arguments passed to jobs are now deep-frozen, to prevent unexpected behavior when the args are mutated and the job is reenqueued.
+
+    *   Since JSONB is now used to store arguments, the order of argument hashes is no longer maintained.
+
+        *   It wouldn't have been a good idea to rely on this anyway.
+
+    *   Calling Que.log() directly is no longer supported/recommended.
+
+    *   Features marked as deprecated in the final 0.x releases have been removed.
+
+*   Finally, if you've built up your own tooling and customizations around Que, you may need to be aware of some DB schema changes made in the migration to schema version #4.
+
+    *   The `job_id` column has been renamed `id` and is now the primary key. This makes it easier to manage the queue using an ActiveRecord model.
+
+    *   Finished jobs are now kept in the DB, unless you explicitly call `destroy`. If you want to query the DB for only jobs that haven't finished yet, add a `WHERE finished_at IS NULL` condition to your query, or use the not_finished scope on one of the provided ORM models.
+
+    *   There is now an `expired_at` timestamp column, which is set when a job reaches its maximum number of retries and will not be attempted again.
+
+    *   Due to popular demand, the default queue name is now "default" rather than an empty string. The migration will move pending jobs under the "" queue to the "default" queue.
+
+    *   The `last_error` column has been split in two, to `last_error_message` and `last_error_backtrace`. These two columns are now limited to 500 and 10,000 characters, respectively. The migration will split old error data correctly, and truncate it if necessary.
+
+    *   Names for queues and job classes are now limited to 500 characters, which is still far longer than either of these values should reasonably be.
+
+    *   There is now a `data` JSONB column which is used to support various ways of organizing jobs (setting tags on them, etc).
+
+---
 
 ### 0.14.3 (2018-03-02)
 
@@ -120,6 +303,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Recorded error messages are now truncated to the first 500 characters.
 
+---
+
 ### 0.14.2 (2018-01-05)
 
 *   Deprecate the Que.disable_prepared_statements= accessors.
@@ -128,24 +313,34 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Update the generated Rails migration to declare a version. (NARKOZ)
 
+---
+
 ### 0.14.1 (2017-12-14)
 
 *   Fix a bug with typecasting boolean values on Rails 5+.
 
+---
+
 ### 0.14.0 (2017-08-11)
 
 *   Fix incompatibility with Rails 5.1.
 
 *   Drop support for waking an in-process worker when an ActiveRecord transaction commits.
 
+---
+
 ### 0.13.1 (2017-07-05)
 
 *   Fix issue that caused error stacktraces to not be persisted in most cases.
 
+---
+
 ### 0.13.0 (2017-06-08)
 
 *   Fix recurring JSON issues by dropping MultiJson support. Previously MultiJson was detected and used automatically, and now it's just ignored and stdlib JSON used instead, so this shouldn't require any code changes.
 
+---
+
 ### 0.12.3 (2017-06-01)
 
 *   Fix incompatibility with MultiJson introduced by the previous release.
@@ -154,28 +349,40 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Fix security vulnerability in parsing JSON from the DB (by specifying create_additions: false). This shouldn't be a concern unless you were passing untrusted user input in your job arguments. (hmac)
 
+---
+
 ### 0.12.1 (2017-01-22)
 
 *   Fix incompatibility with Rails 5.0. (#166) (nbibler, thedarkone)
 
+---
+
 ### 0.12.0 (2016-09-09)
 
 *   The error_handler configuration option has been renamed to error_notifier, which is more descriptive of what it's actually supposed to do. You can still use error_handler for configuration, but you'll get a warning.
 
 *   Introduced a new framework for handling errors on a per-job basis. See the docs for more information. (#106, #147)
 
+---
+
 ### 0.11.6 (2016-07-01)
 
 *   Fix for operating in nested transactions in Rails 5.0. (#160) (greysteil)
 
+---
+
 ### 0.11.5 (2016-05-13)
 
 *   Fix error when running `que -v`. (#154) (hardbap)
 
+---
+
 ### 0.11.4 (2016-03-03)
 
 *   Fix incompatibility with ActiveRecord 5.0.0.beta3. (#143, #144) (joevandyk)
 
+---
+
 ### 0.11.3 (2016-02-26)
 
 *   Fixed bug with displaying the current version of the que executable. (#122) (hardbap)
@@ -186,14 +393,20 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   String literals are now frozen on Ruby 2.3.
 
+---
+
 ### 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.
 
+---
+
 ### 0.11.0 (2015-09-04)
 
 *   A command-line program has been added that can be used to work jobs in a more flexible manner than the previous rake task. Run `que -h` for more information.
@@ -208,6 +421,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   If it exists, use String#constantize to constantize job classes, since ActiveSupport's constantize method behaves better with Rails' autoloading. (#115, #120) (joevandyk)
 
+---
+
 ### 0.10.0 (2015-03-18)
 
 *   When working jobs via the rake task, Rails applications are now eager-loaded if present, to avoid problems with multithreading and autoloading. (#96) (hmarr)
@@ -216,28 +431,40 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Add Que.transaction() helper method, to aid in transaction management in migrations or when the user's ORM doesn't provide one. (#81)
 
+---
+
 ### 0.9.2 (2015-02-05)
 
 *   Fix a bug wherein the at_exit hook in the railtie wasn't waiting for jobs to finish before exiting.
 
 *   Fix a bug wherein the que:work rake task wasn't waiting for jobs to finish before exiting. (#85) (tycooon)
 
+---
+
 ### 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 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)
 
+---
+
 ### 0.8.2 (2014-10-12)
 
 *   Fix errors raised during rollbacks in the ActiveRecord adapter, which remained silent until Rails 4.2. (#64, #65) (Strech)
 
+---
+
 ### 0.8.1 (2014-07-28)
 
 *   Fix regression introduced in the `que:work` rake task by the `mode` / `worker_count` disentangling in 0.8.0. (#50)
 
+---
+
 ### 0.8.0 (2014-07-12)
 
 *   A callable can now be set as the logger, like `Que.logger = proc { MyLogger.new }`. Que uses this in its Railtie for cleaner initialization, but it is also available for public use.
@@ -246,20 +473,28 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Fixed a similar bug wherein setting a wake_interval during application startup would break worker awakening after the process was forked.
 
+---
+
 ### 0.7.3 (2014-05-19)
 
 *   When mode = :sync, don't touch the database at all when running jobs inline. Needed for ActiveJob compatibility (#46).
 
+---
+
 ### 0.7.2 (2014-05-18)
 
 *   Fix issue wherein intermittent worker wakeups would not work after forking (#44).
 
+---
+
 ### 0.7.1 (2014-04-29)
 
 *   Fix errors with prepared statements when ActiveRecord reconnects to the database. (dvrensk)
 
 *   Don't use prepared statements when inside a transaction. This negates the risk of a prepared statement error harming the entire transaction. The query that benefits the most from preparation is the job-lock CTE, which is never run in a transaction, so the performance impact should be negligible.
 
+---
+
 ### 0.7.0 (2014-04-09)
 
 *   `JobClass.queue(*args)` has been deprecated and will be removed in version 1.0.0. Please use `JobClass.enqueue(*args)` instead.
@@ -270,6 +505,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   The [Pond gem](https://github.com/chanks/pond) is now supported as a connection. It is very similar to the ConnectionPool gem, but creates connections lazily and is dynamically resizable.
 
+---
+
 ### 0.6.0 (2014-02-04)
 
 *   **A schema upgrade to version 3 is required for this release.** See [the migration doc](https://github.com/que-rb/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
@@ -290,6 +527,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Job classes may now define their own logic for determining the retry interval when a job raises an error. See [error handling](https://github.com/que-rb/que/blob/master/docs/error_handling.md) for more information.
 
+---
+
 ### 0.5.0 (2014-01-14)
 
 *   When running a worker pool inside your web process on ActiveRecord, Que will now wake a worker once a transaction containing a queued job is committed. (joevandyk, chanks)
@@ -312,6 +551,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
     Now, when a process exits, if the worker pool is running (whether in a rake task or in a web process) the exit will be stalled until all workers have finished their current jobs. If you have long-running jobs, this may take a long time. If you need the process to exit immediately, you can SIGKILL without any threat of commiting prematurely.
 
+---
+
 ### 0.4.0 (2014-01-05)
 
 *   Que.wake_all! was added, as a simple way to wake up all workers in the pool.
@@ -332,6 +573,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Much more internal cleanup.
 
+---
+
 ### 0.3.0 (2013-12-21)
 
 *   Add Que.stop!, which immediately kills all jobs being worked in the process.
@@ -344,6 +587,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Clean up internals and hammer out several race conditions.
 
+---
+
 ### 0.2.0 (2013-11-30)
 
 *   Officially support JRuby 1.7.5+. Earlier versions may work.
@@ -356,6 +601,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   :sync mode now ignores scheduled jobs (jobs queued with a specific run_at).
 
+---
+
 ### 0.1.0 (2013-11-18)
 
 *   Initial public release, after a test-driven rewrite.
@@ -366,6 +613,8 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
     Added a Railtie for easier setup with Rails, as well as a migration generator.
 
+---
+
 ### 0.0.1 (2013-11-07)
 
 *   Copy-pasted from an app of mine. Very Sequel-specific. Nobody look at it, let's pretend it never happened.

data/Dockerfile

@@ -0,0 +1,20 @@
+FROM ruby:2.7.5-slim-buster@sha256:4cbbe2fba099026b243200aa8663f56476950cc64ccd91d7aaccddca31e445b5 AS base
+
+# Install libpq-dev in our base layer, as it's needed in all environments
+RUN apt-get update \
+  && apt-get install -y libpq-dev \
+  && rm -rf /var/lib/apt/lists/*
+
+ENV RUBY_BUNDLER_VERSION 2.3.7
+RUN gem install bundler -v $RUBY_BUNDLER_VERSION
+
+ENV BUNDLE_PATH /usr/local/bundle
+
+ENV RUBYOPT=-W:deprecated
+
+FROM base AS dev-environment
+
+# Install build-essential and git, as we'd need them for building gems that have native code components
+RUN apt-get update \
+  && apt-get install -y build-essential git \
+  && rm -rf /var/lib/apt/lists/*

data/README.md

@@ -1,54 +1,59 @@
 # Que ![tests](https://github.com/que-rb/que/workflows/tests/badge.svg)
 
-**This README and the rest of the docs on the master branch all refer to Que 1.0, which is currently in beta. If you're using version 0.x, please refer to the docs on [the 0.x branch](https://github.com/que-rb/que/tree/0.x).**
+**This README and the rest of the docs on the master branch all refer to Que 1.0. If you're using version 0.x, please refer to the docs on [the 0.x branch](https://github.com/que-rb/que/tree/0.x).**
 
 *TL;DR: Que is a high-performance job queue that improves the reliability of your application by protecting your jobs with the same [ACID guarantees](https://en.wikipedia.org/wiki/ACID) as the rest of your data.*
 
 Que ("keɪ", or "kay") is a queue for Ruby and PostgreSQL that manages jobs using [advisory locks](http://www.postgresql.org/docs/current/static/explicit-locking.html#ADVISORY-LOCKS), which gives it several advantages over other RDBMS-backed queues:
 
-  * **Concurrency** - Workers don't block each other when trying to lock jobs, as often occurs with "SELECT FOR UPDATE"-style locking. This allows for very high throughput with a large number of workers.
-  * **Efficiency** - Locks are held in memory, so locking a job doesn't incur a disk write. These first two points are what limit performance with other queues. Under heavy load, Que's bottleneck is CPU, not I/O.
-  * **Safety** - If a Ruby process dies, the jobs it's working won't be lost, or left in a locked or ambiguous state - they immediately become available for any other worker to pick up.
+- **Concurrency** - Workers don't block each other when trying to lock jobs, as often occurs with "SELECT FOR UPDATE"-style locking. This allows for very high throughput with a large number of workers.
+- **Efficiency** - Locks are held in memory, so locking a job doesn't incur a disk write. These first two points are what limit performance with other queues. Under heavy load, Que's bottleneck is CPU, not I/O.
+- **Safety** - If a Ruby process dies, the jobs it's working won't be lost, or left in a locked or ambiguous state - they immediately become available for any other worker to pick up.
 
 Additionally, there are the general benefits of storing jobs in Postgres, alongside the rest of your data, rather than in Redis or a dedicated queue:
 
-  * **Transactional Control** - Queue a job along with other changes to your database, and it'll commit or rollback with everything else. If you're using ActiveRecord or Sequel, Que can piggyback on their connections, so setup is simple and jobs are protected by the transactions you're already using.
-  * **Atomic Backups** - Your jobs and data can be backed up together and restored as a snapshot. If your jobs relate to your data (and they usually do), there's no risk of jobs falling through the cracks during a recovery.
-  * **Fewer Dependencies** - If you're already using Postgres (and you probably should be), a separate queue is another moving part that can break.
-  * **Security** - Postgres' support for SSL connections keeps your data safe in transport, for added protection when you're running workers on cloud platforms that you can't completely control.
+- **Transactional Control** - Queue a job along with other changes to your database, and it'll commit or rollback with everything else. If you're using ActiveRecord or Sequel, Que can piggyback on their connections, so setup is simple and jobs are protected by the transactions you're already using.
+- **Atomic Backups** - Your jobs and data can be backed up together and restored as a snapshot. If your jobs relate to your data (and they usually do), there's no risk of jobs falling through the cracks during a recovery.
+- **Fewer Dependencies** - If you're already using Postgres (and you probably should be), a separate queue is another moving part that can break.
+- **Security** - Postgres' support for SSL connections keeps your data safe in transport, for added protection when you're running workers on cloud platforms that you can't completely control.
 
 Que's primary goal is reliability. You should be able to leave your application running indefinitely without worrying about jobs being lost due to a lack of transactional support, or left in limbo due to a crashing process. Que does everything it can to ensure that jobs you queue are performed exactly once (though the occasional repetition of a job can be impossible to avoid - see the docs on [how to write a reliable job](/docs/README.md#writing-reliable-jobs)).
 
 Que's secondary goal is performance. The worker process is multithreaded, so that a single process can run many jobs simultaneously.
 
 Compatibility:
+
 - MRI Ruby 2.2+
 - PostgreSQL 9.5+
 - Rails 4.1+ (optional)
 
 **Please note** - Que's job table undergoes a lot of churn when it is under high load, and like any heavily-written table, is susceptible to bloat and slowness if Postgres isn't able to clean it up. The most common cause of this is long-running transactions, so it's recommended to try to keep all transactions against the database housing Que's job table as short as possible. This is good advice to remember for any high-activity database, but bears emphasizing when using tables that undergo a lot of writes.
 
-
 ## Installation
 
 Add this line to your application's Gemfile:
 
-    gem 'que'
+```ruby
+gem 'que'
+```
 
 And then execute:
 
-    $ bundle
+```bash
+bundle
+```
 
 Or install it yourself as:
 
-    $ gem install que
-
+```bash
+gem install que
+```
 
 ## Usage
 
 First, create the queue schema in a migration. For example:
 
-``` ruby
+```ruby
 class CreateQueSchema < ActiveRecord::Migration[5.0]
   def up
     # Whenever you use Que in a migration, always specify the version you're
@@ -66,7 +71,7 @@ end
 
 Create a class for each type of job you want to run:
 
-``` ruby
+```ruby
 # app/jobs/charge_credit_card.rb
 class ChargeCreditCard < Que::Job
   # Default settings for this job. These are optional - without them, jobs
@@ -101,7 +106,7 @@ end
 
 Queue your job. Again, it's best to do this in a transaction with other changes you're making. Also note that any arguments you pass will be serialized to JSON and back again, so stick to simple types (strings, integers, floats, hashes, and arrays).
 
-``` ruby
+```ruby
 CreditCard.transaction do
   # Persist credit card information
   card = CreditCard.create(params[:credit_card])
@@ -111,17 +116,18 @@ end
 
 You can also add options to run the job after a specific time, or with a specific priority:
 
-``` ruby
+```ruby
 ChargeCreditCard.enqueue card.id, user_id: current_user.id, run_at: 1.day.from_now, priority: 5
 ```
 ## Running the Que Worker
 In order to process jobs, you must start a separate worker process outside of your main server. 
 
-```
+```bash
 bundle exec que
 ```
 
 Try running `que -h` to get a list of runtime options:
+
 ```
 $ que -h
 usage: que [options] [file/to/require] ...
@@ -138,21 +144,24 @@ If you're using ActiveRecord to dump your database's schema, please [set your sc
 
 Pre-1.0, the default queue name needed to be configured in order for Que to work out of the box with Rails. In 1.0 the default queue name is now 'default', as Rails expects, but when Rails enqueues some types of jobs it may try to use another queue name that isn't worked by default. You can either:
 
-* [Configure Rails](https://guides.rubyonrails.org/configuring.html) to send all internal job types to the 'default' queue by adding the following to `config/application.rb`:
-```ruby
-config.action_mailer.deliver_later_queue_name = :default
-config.action_mailbox.queues.incineration = :default
-config.action_mailbox.queues.routing = :default
-config.active_storage.queues.analysis = :default
-config.active_storage.queues.purge = :default
-```
+- [Configure Rails](https://guides.rubyonrails.org/configuring.html) to send all internal job types to the 'default' queue by adding the following to `config/application.rb`:
 
-* [Tell que](/docs#multiple-queues) to work all of these queues (less efficient because it requires polling all of them):
-```
-que -q default -q mailers -q action_mailbox_incineration -q action_mailbox_routing -q active_storage_analysis -q active_storage_purge
-```
+    ```ruby
+    config.action_mailer.deliver_later_queue_name = :default
+    config.action_mailbox.queues.incineration = :default
+    config.action_mailbox.queues.routing = :default
+    config.active_storage.queues.analysis = :default
+    config.active_storage.queues.purge = :default
+    ```
+
+- [Tell que](/docs#multiple-queues) to work all of these queues (less efficient because it requires polling all of them):
+
+    ```bash
+    que -q default -q mailers -q action_mailbox_incineration -q action_mailbox_routing -q active_storage_analysis -q active_storage_purge
+    ```
 
 Also, if you would like to integrate Que with Active Job, you can do it by setting the adapter in `config/application.rb` or in a specific environment by setting it in `config/environments/production.rb`, for example:
+
 ```ruby
 config.active_job.queue_adapter = :que
 ```
@@ -183,9 +192,9 @@ If you have a project that uses or relates to Que, feel free to submit a PR addi
 
 ## Community and Contributing
 
-  * For bugs in the library, please feel free to [open an issue](https://github.com/que-rb/que/issues/new).
-  * For general discussion and questions/concerns that don't relate to obvious bugs, join our [Discord Server](https://discord.gg/B3EW32H).
-  * For contributions, pull requests submitted via Github are welcome.
+- For bugs in the library, please feel free to [open an issue](https://github.com/que-rb/que/issues/new).
+- For general discussion and questions/concerns that don't relate to obvious bugs, join our [Discord Server](https://discord.gg/B3EW32H).
+- For contributions, pull requests submitted via Github are welcome.
 
 Regarding contributions, one of the project's priorities is to keep Que as simple, lightweight and dependency-free as possible, and pull requests that change too much or wouldn't be useful to the majority of Que's users have a good chance of being rejected. If you're thinking of submitting a pull request that adds a new feature, consider starting a discussion in [que-talk](https://groups.google.com/forum/#!forum/que-talk) first about what it would do and how it would be implemented. If it's a sufficiently large feature, or if most of Que's users wouldn't find it useful, it may be best implemented as a standalone gem, like some of the related projects above.
 
@@ -193,12 +202,54 @@ 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. 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 SEED=$i bundle exec rake; done
+```bash
+for i in {1..1000}; do SEED=$i bundle exec rake; 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 SEED=328 bundle exec rake; done
+```bash
+for i in {1..1000}; do LOG_SPEC=true SEED=328 bundle exec rake; 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.
 
 Another helpful technique is to replace an `it` spec declaration with `hit` - this will run that particular spec 100 times during the run.
+
+#### With Docker
+
+We've provided a Dockerised environment to avoid the need to manually: install Ruby, install the gem bundle, set up Postgres, and connect to the database.
+
+To run the specs using this environment, run:
+
+```bash
+./auto/test
+```
+
+To get a shell in the environment, run:
+
+```bash
+./auto/dev
+```
+
+The [Docker Compose config](docker-compose.yml) provides a convenient way to inject your local shell aliases into the Docker container. Simply create a file containing your alias definitions (or which sources them from other files) at `~/.docker-rc.d/.docker-bashrc`, and they will be available inside the container.
+
+#### Without Docker
+
+You'll need to have Postgres running. Assuming you have it running on port 5697, with a `que-test` database, and a username & password of `que`, you can run:
+
+```bash
+DATABASE_URL=postgres://que:que@localhost:5697/que-test bundle exec rake
+```
+
+If you don't already have Postgres, you could use Docker Compose to run just the database:
+
+```bash
+docker compose up -d db
+```
+
+If you want to try a different version of Postgres, e.g. 12:
+
+```bash
+export POSTGRES_VERSION=12
+```

data/auto/dev

@@ -0,0 +1,21 @@
+#!/bin/bash
+#
+# Operate in development environment
+
+set -Eeuo pipefail
+
+cd "$(dirname "$0")/.."
+
+docker compose build dev
+
+# Delete containers and DB volume afterwards on CI
+if [[ "${CI-}" == "true" ]]; then
+  trap '{
+    echo "Stopping containers..."
+    docker compose down
+    docker volume rm -f que_db-data
+  }' EXIT
+fi
+
+set -x
+docker compose run --rm dev "${@-bash}"

data/auto/psql

@@ -0,0 +1,9 @@
+#!/bin/bash
+#
+# Open a database shell
+
+set -Eeuo pipefail
+
+cd "$(dirname "$0")/.."
+
+docker compose run --rm pg-dev psql "${@-}"

data/auto/test

@@ -0,0 +1,5 @@
+#!/bin/bash
+
+set -Eeuo pipefail
+
+"$(dirname "$0")"/dev ./scripts/test "$@"

data/auto/test-postgres-14

@@ -0,0 +1,17 @@
+#!/bin/bash
+
+set -Eeuo pipefail
+
+export POSTGRES_VERSION=14
+
+delete_db() {
+  docker compose down
+  docker volume rm -f que_db-data
+}
+
+trap delete_db EXIT
+
+# pre-test cleanup is necessary as the existing db container will be used if it's running (potentially with the wrong PG version)
+delete_db
+"$(dirname "$0")"/test "$@"
+delete_db

data/docker-compose.yml

@@ -0,0 +1,46 @@
+version: "3.7"
+
+services:
+
+  dev:
+    build:
+      context: .
+      target: dev-environment
+    depends_on:
+      - db
+    volumes:
+      - .:/work
+      - ruby-2.7.5-gem-cache:/usr/local/bundle
+      - ~/.docker-rc.d/:/.docker-rc.d/:ro
+    working_dir: /work
+    entrypoint: /work/scripts/docker-entrypoint
+    command: bash
+    environment:
+      DATABASE_URL: postgres://que:que@db/que-test
+
+  db:
+    image: "postgres:${POSTGRES_VERSION-13}"
+    volumes:
+      - db-data:/var/lib/postgresql/data
+    environment:
+      POSTGRES_USER: que
+      POSTGRES_PASSWORD: que
+      POSTGRES_DB: que-test
+    ports:
+      - 5697:5432
+
+  pg-dev:
+    image: "postgres:${POSTGRES_VERSION-13}"
+    depends_on:
+      - db
+    entrypoint: []
+    command: psql
+    environment:
+      PGHOST: db
+      PGUSER: que
+      PGPASSWORD: que
+      PGDATABASE: que-test
+
+volumes:
+  db-data: ~
+  ruby-2.7.5-gem-cache: ~

data/lib/que/job.rb

@@ -57,22 +57,18 @@ module Que
 
       def enqueue(
         *args,
-        queue:     nil,
-        priority:  nil,
-        run_at:    nil,
-        job_class: nil,
-        tags:      nil,
+        job_options: {},
         **arg_opts
       )
-
+        arg_opts, job_options = _extract_job_options(arg_opts, job_options.dup)
         args << arg_opts if arg_opts.any?
 
-        if tags
-          if tags.length > MAXIMUM_TAGS_COUNT
-            raise Que::Error, "Can't enqueue a job with more than #{MAXIMUM_TAGS_COUNT} tags! (passed #{tags.length})"
+        if job_options[:tags]
+          if job_options[:tags].length > MAXIMUM_TAGS_COUNT
+            raise Que::Error, "Can't enqueue a job with more than #{MAXIMUM_TAGS_COUNT} tags! (passed #{job_options[:tags].length})"
           end
 
-          tags.each do |tag|
+          job_options[:tags].each do |tag|
             if tag.length > MAXIMUM_TAG_LENGTH
               raise Que::Error, "Can't enqueue a job with a tag longer than 100 characters! (\"#{tag}\")"
             end
@@ -80,13 +76,13 @@ module Que
         end
 
         attrs = {
-          queue:    queue    || resolve_que_setting(:queue) || Que.default_queue,
-          priority: priority || resolve_que_setting(:priority),
-          run_at:   run_at   || resolve_que_setting(:run_at),
+          queue:    job_options[:queue]    || resolve_que_setting(:queue) || Que.default_queue,
+          priority: job_options[:priority] || resolve_que_setting(:priority),
+          run_at:   job_options[:run_at]   || resolve_que_setting(:run_at),
           args:     Que.serialize_json(args),
-          data:     tags ? Que.serialize_json(tags: tags) : "{}",
+          data:     job_options[:tags] ? Que.serialize_json(tags: job_options[:tags]) : "{}",
           job_class: \
-            job_class || name ||
+            job_options[:job_class] || name ||
               raise(Error, "Can't enqueue an anonymous subclass of Que::Job"),
         }
 
@@ -139,6 +135,27 @@ module Que
           end
         end
       end
+
+      def _extract_job_options(arg_opts, job_options)
+        deprecated_job_option_names = []
+
+        %i[queue priority run_at job_class tags].each do |option_name|
+          next unless arg_opts.key?(option_name) && job_options[option_name].nil?
+
+          job_options[option_name] = arg_opts.delete(option_name)
+          deprecated_job_option_names << option_name
+        end
+
+        _log_job_options_deprecation(deprecated_job_option_names)
+
+        [arg_opts, job_options]
+      end
+
+      def _log_job_options_deprecation(deprecated_job_option_names)
+        return unless deprecated_job_option_names.any?
+
+        warn "Passing job options like (#{deprecated_job_option_names.join(', ')}) to `JobClass.enqueue` as top level keyword args has been deprecated and will be removed in version 2.0. Please wrap job options in an explicit `job_options` keyword arg instead."
+      end
     end
 
     # Set up some defaults.

data/lib/que/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Que
-  VERSION = '1.0.0.beta5'
+  VERSION = '1.2.0'
 end

data/lib/que/worker.rb

@@ -137,6 +137,7 @@ module Que
         error: {
           class:   error.class.to_s,
           message: error.message,
+          backtrace: (error.backtrace || []).join("\n").slice(0, 10000),
         },
       )
 
@@ -164,7 +165,7 @@ module Que
           Que.execute :set_error, [
             delay,
             "#{error.class}: #{error.message}".slice(0, 500),
-            error.backtrace.join("\n").slice(0, 10000),
+            (error.backtrace || []).join("\n").slice(0, 10000),
             job.fetch(:id),
           ]
         end

data/scripts/docker-entrypoint

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+set -Eeuo pipefail
+
+# For using your own dotfiles within the Docker container
+if [ -f /.docker-rc.d/.docker-bashrc ]; then
+  echo "source /.docker-rc.d/.docker-bashrc" >> ~/.bashrc
+fi
+
+gem list -i -e bundler -v "$RUBY_BUNDLER_VERSION" >/dev/null || gem install bundler -v "$RUBY_BUNDLER_VERSION"
+
+bundle check --dry-run || bundle install
+
+exec "${@-bash}"

data/scripts/test

@@ -0,0 +1,5 @@
+#!/bin/bash
+
+set -Eeuo pipefail
+
+bundle exec rake spec "$@"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: que
 version: !ruby/object:Gem::Version
-  version: 1.0.0.beta5
+  version: 1.2.0
 platform: ruby
 authors:
 - Chris Hanks
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-12-23 00:00:00.000000000 Z
+date: 2022-02-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -34,13 +34,18 @@ extra_rdoc_files: []
 files:
 - ".github/workflows/tests.yml"
 - ".gitignore"
-- CHANGELOG.1.0.beta.md
 - CHANGELOG.md
+- Dockerfile
 - LICENSE.txt
 - README.md
 - Rakefile
+- auto/dev
+- auto/psql
+- auto/test
+- auto/test-postgres-14
 - bin/command_line_interface.rb
 - bin/que
+- docker-compose.yml
 - docs/README.md
 - lib/que.rb
 - lib/que/active_job/extensions.rb
@@ -80,11 +85,13 @@ files:
 - lib/que/version.rb
 - lib/que/worker.rb
 - que.gemspec
+- scripts/docker-entrypoint
+- scripts/test
 homepage: https://github.com/que-rb/que
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -95,12 +102,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: []
 rubygems_version: 3.1.6
-signing_key: 
+signing_key:
 specification_version: 4
 summary: A PostgreSQL-based Job Queue
 test_files: []

data/CHANGELOG.1.0.beta.md

@@ -1,137 +0,0 @@
-### 1.0.0.beta3 (2018-05-18)
-
-*   Added support for customizing log levels for `job_worked` events (#217).
-
-*   Began logging all `job_errored` events at the `ERROR` log level.
-
-*   Fixed the Railtie when running in test mode (#214).
-
-*   Tweaked the meanings of worker-priorities and worker-count options in the CLI, to better support use cases with low worker counts (#216).
-
-### 1.0.0.beta2 (2018-04-13)
-
-*   Fixed an incompatibility that caused the new locker to hang when using Rails in development mode (#213).
-
-*   Fixed a bug with setting the log level via the CLI when the configured logger was based on a callable (#210).
-
-*   Renamed Que.middleware to Que.job_middleware.
-
-*   Added Que.sql_middleware.
-
-*   Officially added support for Ruby 2.5.
-
-*   Internal cleanup and renamings.
-
-### 1.0.0.beta (2017-10-25)
-
-*   **A schema upgrade to version 4 will be required for this release.** See [the migration doc](https://github.com/que-rb/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
-
-    *   Please note that this migration requires a rewrite of the jobs table, which makes it O(n) with the size of the table. If you have a very large backlog of jobs you may want to schedule downtime for this migration.
-
-*   Que's implementation has been changed from one in which worker threads hold their own PG connections and lock their own jobs to one in which a single thread (and PG connection) locks jobs through LISTEN/NOTIFY and batch polling, and passes jobs along to worker threads. This has many benefits, including:
-
-    *   Jobs queued for immediate processing can be actively distributed to workers with LISTEN/NOTIFY, which is more efficient than having workers repeatedly poll for new jobs.
-
-    *   When polling is necessary (to pick up jobs that are scheduled for the future or that need to be retried due to errors), jobs can be locked and fetched in batches, rather than one at a time.
-
-    *   Individual workers no longer need to monopolize their own (usually idle) connections while working jobs, so Ruby processes will require fewer Postgres connections.
-
-    *   PgBouncer or another external connection pool can be used for workers' connections (though not for the connection used to lock and listen for jobs).
-
-*   Other features introduced in this version include:
-
-    *   Much better support for all versions of ActiveJob.
-
-        *   In particular, you may (optionally) include `Que::ActiveJob::JobExtensions` into `ApplicationJob` to get support for all of Que's job helper methods.
-
-    *   Custom middleware that wrap running jobs are now supported.
-
-    *   Support for categorizing jobs with tags.
-
-    *   Support for configuring a `maximum_retry_count` on individual job classes.
-
-    *   Job configuration options are now inheritable, so job class hierarchies are more useful.
-
-    *   There are now built-in models for ActiveRecord and Sequel to allow inspecting the queue easily.
-
-    *   Jobs that have finished working may optionally be retained in the database indefinitely.
-
-        *   To keep a job record, replace the `destroy` calls in your jobs with `finish`. `destroy` will still delete records entirely, for jobs that you don't want to keep.
-
-        *   If you don't resolve a job yourself one way or another, Que will still `destroy` the job for you by default.
-
-        *   Finished jobs have a timestamp set in the finished_at column.
-
-    *   Jobs that have errored too many times will now be marked as expired, and won't be retried again.
-
-        *   You can configure a maximum_retry_count in your job classes, to set the threshold at which a job will be marked expired. The default is 15.
-
-        *   To manually mark a job as expired (and keep it in the database but not try to run it again) you can call `expire` helper in your job.
-
-    *   You can now set job priority thresholds for individual workers, to ensure that there will always be space available for high-priority jobs.
-
-    *   `Que.job_states` returns a list of locked jobs and the hostname/pid of the Ruby processes that have locked them.
-
-    *   `Que.connection_proc=` has been added, to allow for the easy integration of custom connection pools.
-
-*   In keeping with semantic versioning, the major version is being bumped since the new implementation requires some backwards-incompatible changes. These changes include:
-
-    *   Support for MRI Rubies before 2.2 has been dropped.
-
-    *   Support for Postgres versions before 9.5 has been dropped (JSONB and upsert support is required).
-
-    *   JRuby support has been dropped. It will be reintroduced whenever the jruby-pg gem is production-ready.
-
-    *   The `que:work` rake task has been removed. Use the `que` executable instead.
-
-        *   Therefore, configuring workers using QUE_* environment variables is no longer supported. Please pass the appropriate options to the `que` executable instead.
-
-    *   The `mode` setter has been removed.
-
-        *   To run jobs synchronously when they are enqueued (the old `:sync` behavior) you can set `Que.run_synchronously = true`.
-
-        *   To start up the worker pool (the old :async behavior) you should use the `que` executable to start up a worker process. There's no longer a supported API for running workers outside of the `que` executable.
-
-    *   The following methods are not meaningful under the new implementation and have been removed:
-
-        *   The `Que.wake_interval` getter and setter.
-
-        *   The `Que.worker_count` getter and setter.
-
-        *   `Que.wake!`
-
-        *   `Que.wake_all!`
-
-    *   Since Que needs a dedicated Postgres connection to manage job locks, running Que through a single PG connection is no longer supported.
-
-        *   It's not clear that anyone ever actually did this.
-
-    *   `Que.worker_states` has been removed, as the connection that locks a job is no longer the one that the job is using to run. Its functionality has been partially replaced with `Que.job_states`.
-
-    *   When using Rails, for simplicity, job attributes and keys in argument hashes are now converted to symbols when retrieved from the database, rather than being converted to instances of HashWithIndifferentAccess.
-
-    *   Arguments passed to jobs are now deep-frozen, to prevent unexpected behavior when the args are mutated and the job is reenqueued.
-
-    *   Since JSONB is now used to store arguments, the order of argument hashes is no longer maintained.
-
-        *   It wouldn't have been a good idea to rely on this anyway.
-
-    *   Calling Que.log() directly is no longer supported/recommended.
-
-    *   Features marked as deprecated in the final 0.x releases have been removed.
-
-*   Finally, if you've built up your own tooling and customizations around Que, you may need to be aware of some DB schema changes made in the migration to schema version #4.
-
-    *   The `job_id` column has been renamed `id` and is now the primary key. This makes it easier to manage the queue using an ActiveRecord model.
-
-    *   Finished jobs are now kept in the DB, unless you explicitly call `destroy`. If you want to query the DB for only jobs that haven't finished yet, add a `WHERE finished_at IS NULL` condition to your query, or use the not_finished scope on one of the provided ORM models.
-
-    *   There is now an `expired_at` timestamp column, which is set when a job reaches its maximum number of retries and will not be attempted again.
-
-    *   Due to popular demand, the default queue name is now "default" rather than an empty string. The migration will move pending jobs under the "" queue to the "default" queue.
-
-    *   The `last_error` column has been split in two, to `last_error_message` and `last_error_backtrace`. These two columns are now limited to 500 and 10,000 characters, respectively. The migration will split old error data correctly, and truncate it if necessary.
-
-    *   Names for queues and job classes are now limited to 500 characters, which is still far longer than either of these values should reasonably be.
-
-    *   There is now a `data` JSONB column which is used to support various ways of organizing jobs (setting tags on them, etc).