resque-scheduler

resque-scheduler copied to clipboard

Resque.enqueue_at accepts ActiveRecord::Duration without erroring

2

Hello, Resque.enqueue_in and Resque.enqueue_at are very similar, and I've seen bugs where an `ActiveRecord::Duration` is passed to `Resque.enqueue_at` accidentally. However, no error happens. My suggestion is to add validation that...

carmi

change dynamic schedule set_schedule default persist

1

To improve the incompatible problem #633

ceshihao

scheduler can NOT enqueue job correctly sometimes

5

I use `resque-scheduler` v4.0.0 Recently, my resque scheduler can NOT enqueue jobs correctly sometimes. There are 3 phenomenons, but i can NOT find root cause so far. 1. Sometimes, all...

ceshihao

Note about Resque.redis config

4

In regards to #468. I missed that resque-scheduler was _completely_ stand-alone and wouldn't catch on to that I use a different redis database other than the default 0 for resque...

danlo

Default quiet=false when background with logfile

6

Closes #565

meatballhat

This fixes the non cleanup of Resque scheduled sets where the encoded job in the scheduled list and job set were different. In our setup because of the encoded keys...

kamaljoshi

Fixes #504 for recurring jobs. I'm not sure if the behavior should be the same for delayed jobs. Can be added easily, though.

peret

Support Duration for jobs periodicity

1

Instead of doing ```ruby name = 'send_emails' config = {} config[:class] = 'SendEmail' config[:args] = 'POC email subject' config[:every] = ['1h', {first_in: 5.minutes}] config[:persist] = true Resque.set_schedule(name, config) ``` it...

AlexandreKueny

Cached config doesn't use a master prefix

4

We use the RESQUE_SCHEDULER_MASTER_LOCK_PREFIX feature to run multiple schedulers on one redis instance. But, we've noticed that resque scheduler puts a cache of the config in "resque:schedule", with no prefix....

hlascelles

Persisted Dynamically created job prevents scheduler from starting

3

I created a repeating job dynamically, which worked well. The job started after the given `first_at` time and everything was peachy. The job was persisted, as I wanted it to...

dwillie