que 1.0.0.beta3 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 832beb15feb06f24511a7adec121b635639a87449f1403dcf8763cf8517ab11c
-  data.tar.gz: d39465285d79a8348753e4783a22c7432f369dc8ce0205c41872a87798cd5b48
+  metadata.gz: 2be51744809f55950825aa7bbb6c3e4d7d4d0927a439dfdf2c1f3658f53cfc84
+  data.tar.gz: f1c7b10f27e57fd11288f50789cef31574e11a333733dfbae93e870841dabf28
 SHA512:
-  metadata.gz: bb927afb7f17dd55a2207686f2707bb994860a6c4a4fa2a30e79fb763a7d298b410e3dec36d4520b7617e996e7927b8b90c8fa1ab68a3e264d96b59df9c51a4d
-  data.tar.gz: 421aaa5ce29afb83ac376966b2f859a4ba356087fad248738a57b3e9c77bb193ee8f08d58320ec10b6aa9bb3587c9c05bf6c9d7a22c6da62d908ef6876cdd173
+  metadata.gz: 93688d24737b750e85c1769bebc6d1344264a8b9757c855150c1dd022104a6400e205442db443bf12c8623325a8178b5379ff647faecd47ada873ead78d5ce7e
+  data.tar.gz: 7fc7c9e34adb2f779f947c0d8326da32c40ba47c7fe4501e343fc177d3115275a25e28b8b407aa62a3ce7d095760f4f392fb9f501892918fc5d2dc3802871f93

data/.github/workflows/tests.yml

@@ -0,0 +1,43 @@
+name: tests
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby_version: [2.5.x, 2.6.x, 2.7.x]
+        gemfile: ["4.2", "5.2", "6.0"]
+        postgres_version: [9, 10, 11, 12]
+        exclude:
+          - { gemfile: "4.2", ruby_version: "2.7.x" }
+    services:
+      db:
+        image: postgres:${{ matrix.postgres_version }}
+        env:
+          POSTGRES_HOST_AUTH_METHOD: trust
+        ports: ['5432:5432']
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+    steps:
+    - uses: actions/checkout@v1
+    - name: Set up Ruby
+      uses: actions/setup-ruby@v1
+      with:
+        ruby-version: ${{ matrix.ruby_version }}
+    - name: Test with Rake
+      env:
+        PGHOST: 127.0.0.1
+        PGUSER: postgres
+        BUNDLE_GEMFILE: spec/gemfiles/Gemfile.${{ matrix.gemfile }}
+      run: |
+        sudo apt-get -yqq install libpq-dev postgresql-client
+        createdb que-test
+        gem install bundler
+        bundle install --jobs 4 --retry 3
+        USE_RAILS=true bundle exec rake test
+        bundle exec rake test

data/CHANGELOG.md

@@ -1,6 +1,69 @@
+### 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/chanks/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
+*   **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.
 
@@ -96,6 +159,121 @@
 
     *   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).
+---
+
+### 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.
@@ -112,7 +290,7 @@
 
     *   There is now a `data` JSONB column which is used to support various ways of organizing jobs (setting tags on them, etc).
 
-For a detailed list of the changes between each beta release of 1.0.0, see [the beta Changelog](CHANGELOG.1.0.beta.md).
+---
 
 ### 0.14.3 (2018-03-02)
 
@@ -120,6 +298,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 +308,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 +344,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 +388,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 +416,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 +426,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 +468,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,9 +500,11 @@ 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/chanks/que/blob/master/docs/migrating.md) for information if you're upgrading from a previous release.
+*   **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.
 
 *   You can now run a job's logic directly (without enqueueing it) like `MyJob.run(arg1, arg2, other_arg: arg3)`. This is useful when a job class encapsulates logic that you want to invoke without involving the entire queue.
 
@@ -284,11 +516,13 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Log lines now include the machine's hostname, since a pid alone may not uniquely identify a process.
 
-*   Multiple queues are now supported. See [the docs](https://github.com/chanks/que/blob/master/docs/multiple_queues.md) for details. (chanks, joevandyk)
+*   Multiple queues are now supported. See [the docs](https://github.com/que-rb/que/blob/master/docs/multiple_queues.md) for details. (chanks, joevandyk)
 
 *   Rubinius 2.2 is now supported. (brixen)
 
-*   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/chanks/que/blob/master/docs/error_handling.md) for more information.
+*   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)
 
@@ -302,7 +536,7 @@ For a detailed list of the changes between each beta release of 1.0.0, see [the
 
 *   Added a migration system to make it easier to change the schema when updating Que. You can now write, for example, `Que.migrate!(version: 2)` in your migrations. Migrations are run transactionally.
 
-*   The logging format has changed to be more easily machine-readable. You can also now customize the logging format by assigning a callable to Que.log_formatter=. See the new doc on [logging](https://github.com/chanks/que/blob/master/docs/logging.md)) for details. The default logger level is INFO - for less critical information (such as when no jobs were found to be available or when a job-lock race condition has been detected and avoided) you can set the QUE_LOG_LEVEL environment variable to DEBUG.
+*   The logging format has changed to be more easily machine-readable. You can also now customize the logging format by assigning a callable to Que.log_formatter=. See the new doc on [logging](https://github.com/que-rb/que/blob/master/docs/logging.md)) for details. The default logger level is INFO - for less critical information (such as when no jobs were found to be available or when a job-lock race condition has been detected and avoided) you can set the QUE_LOG_LEVEL environment variable to DEBUG.
 
 *   MultiJson is now a soft dependency. Que will use it if it is available, but it is not required.
 
@@ -312,6 +546,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 +568,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 +582,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 +596,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 +608,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/*