Releases: rainforestapp/queue_classic_plus
Releases · rainforestapp/queue_classic_plus
[v4.0.0.alpha21] - Properly memoize failed job class
What's Changed
Full Changelog: v4.0.0.alpha20...v4.0.0.alpha21
[v4.0.0.alpha20] - Handle failed non-QC+ jobs
[4.0.0-alpha19] Add callbacks to enqueue and perform
Changes
Adds callbacks:
before_enqueue
after_enqueue
before_perform
after_perform
Allowing jobs to do any pre/post processing.
[4.0.0-alpha18] Revert to 4.0.0.alpha13 implementation
Changes
Reverts to implementation in 4.0.0.alpha13 which was the last stable release. https://github.com/rainforestapp/queue_classic_plus/releases/tag/v4.0.0.alpha13
[4.0.0-alpha17] Fix lock! thread safety performance
Fixes
- https://github.com/rainforestapp/queue_classic_plus/releases/tag/v4.0.0.alpha14 caused a performance issue with too much locking on the queue. This is re-implements thread safety on
lock!without using transaction locks.
Changes
QUEUE_CLASSIC_MAX_LOCK_TIMEis no longer supported and jobs withlock!will not have a timeout. This feature was inherently dangerous in that alock!job should never have more than 1 instance enqueued.
[4.0.0-alpha16] Hotfix queue_name_digest out of range
Fixes
- https://github.com/rainforestapp/queue_classic_plus/releases/tag/v4.0.0.alpha14 had an error where the queue_name_digest could go out of range of postgres bigint. This fixes it.
[4.0.0-alpha15] Hotfix transaction error
Fixes
- https://github.com/rainforestapp/queue_classic_plus/releases/tag/v4.0.0.alpha14 introduced an error when
Job.dowas called within a transaction. This fixes it.
[4.0.0-alpha14] Fix lock! thread safety
Fixes
- Fix lock! not being thread safe. It was possible for 2 jobs to be enqueued even with
lock!on the job ifjob.dowas called simultaneously from different threads.
[4.0.0-alpha13] dry-configurable dependency hotfix
Fixes
- Fix missing dependency for
dry-configurable
[4.0.0-alpha12] Configure Datadog service name
New
- Support configuration of Datadog service name to override the default
qc.job.