David Stosik a2dd36c6d1 MyWorker.perform_in(1.month) does not always schedule job in one month. ... At the moment, `MyWorker.perform_in(1.month)` always schedules a job in 30 days. When added to a date, `1.month` will add 1 to the date's month count, which means that it will add 28, 29, 30, or 31 days depending on the month and year. When I call `MyWorker.perform_in(1.month)`, I would expect the job to be scheduled next month, same day of the month, all the time. At the moment, it is true only four months in the year. My pull request tries to fix this by converting the interval object to a Float at the last possible moment. Plaese note that the test I wrote will fail only during months that do not have 30 days. Ideally, I would add a dependency to Timecop and freeze time to any day in a month of 28, 29 or 31 days. This could also avoid using `#assert_in_delta`, in favour of `#assert_equal`. Feel free to read my blog post [Rails' `1.month` has a variable length](http://dstosik.github.io/rails/2015/02/19/rails-1month-variable-length/) for more details.		2015-02-20 09:36:32 +09:00
..
generators/sidekiq	Update generator generated test file naming	2014-10-21 17:07:43 +08:00
sidekiq	MyWorker.perform_in(1.month) does not always schedule job in one month.	2015-02-20 09:36:32 +09:00
sidekiq.rb	Allows configuration of the Dead Job Queue.	2015-02-04 15:34:31 -05:00