Recently, I upgraded sidekiq gem in my app. Hence, I upgraded subsequent dependent gems as well including sidekiq-unique-jobs.
Following is the snapshot of sidekiq related gems in Gemfile.lock:

When I ran specs that tests one of the unique jobs, it failed giving error:
ArgumentError:
wrong number of arguments (given 1, expected 3)
# ./lib/jobs/worker.rb:7:in `unique_args'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:123:in `filter_by_symbol'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:97:in `filtered_args'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:57:in `unique_args'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:24:in `block in initialize'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/logging.rb:32:in `with_context'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:20:in `initialize'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:16:in `new'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/unique_args.rb:16:in `digest'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/lock/while_executing.rb:44:in `create_digest'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/lock/while_executing.rb:12:in `initialize'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/options_with_fallback.rb:21:in `new'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/options_with_fallback.rb:21:in `lock'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/client/middleware.rb:30:in `acquire_lock'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/client/middleware.rb:26:in `disabled_or_successfully_locked?'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-unique-jobs-4.0.17/lib/sidekiq_unique_jobs/client/middleware.rb:18:in `call'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-pro-3.3.1/lib/sidekiq/batch/middleware.rb:15:in `call'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/middleware/chain.rb:133:in `invoke'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/client.rb:205:in `process_single'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/client.rb:65:in `push'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/worker.rb:116:in `client_push'
# /Users/.rvm/gems/ruby-2.3.1/gems/sidekiq-4.1.2/lib/sidekiq/worker.rb:60:in `perform_async'
I suspect it to be because of sidekiq version. I am still debugging it but does anyone have any idea?
Is latest version of sidekiq-unique-jobs compatible with latest version of sidekiq?
Recently, I upgraded sidekiq gem in my app. Hence, I upgraded subsequent dependent gems as well including
sidekiq-unique-jobs.Following is the snapshot of sidekiq related gems in Gemfile.lock:
When I ran specs that tests one of the unique jobs, it failed giving error:
I suspect it to be because of sidekiq version. I am still debugging it but does anyone have any idea?
Is latest version of
sidekiq-unique-jobscompatible with latest version ofsidekiq?