Artur Trzop

You don't need refresh because you can use function as a min/max value. Here is a nice topic about it http://stackoverflow.com/a/19281903/905697

Sounds fine.

Support for multiple organisations would help a lot when you are working on multiple projects across different organisations. I've extracted an issue for that https://github.com/nolaneo/SeaEye/issues/10

I would expect that `refuse_coverage_drop` should generate "coverage/.last_run.json" file as stated here https://coderwall.com/p/ki2sdq/simplecov-prevent-coverage-drop ```ruby require 'knapsack_pro' SimpleCov.start 'rails' do add_filter [ "lib/analytics/", "lib/data_migrations/", "lib/data_restoration/", "lib/tasks/turnstone.rake", "spec/", ] refuse_coverage_drop # this...

I used to have this idea. To achieve sequential jobs I could use semaphore ( https://github.com/dv/redis-semaphore ) so that if 2 jobs are running at the same time only one...

Thanks @holstvoogd It looks like `Sidekiq::Throttled` could enforce one job at a time.

After the gem upgrade I noticed this issue (in rails console): ``` 3.0.1 :001 > Worker.perform_async("223") /Users/artur/.rvm/gems/ruby-3.0.1/gems/redis-4.3.1/lib/redis.rb:1291:in `>': no implicit conversion of Integer into Hash (TypeError) 3.0.1 :002 > Worker.perform_async(223)...

Here is my worker: ```ruby class MyWorker include Sidekiq::Worker sidekiq_options queue: :my_queue_name, # Locks when the client pushes the job to the queue. # The queue will be unlocked when...

I can confirm v7.1.1 works fine now. Thanks :)

@mhenrixon I have a different error this time. Some of the jobs are timeouting due to the issue to connect with Redis. It's recommended to use a higher timeout for...