v7.0.0.beta15 Can't push new jobs to queue

[eni9889]

Describe the bug
After some time I am now unable to push any new jobs to a queue. I see no debug messages. When I call perform_asyc on the unique worker I get back a digest but no job is added to the queue. The issue continues even if I remove the lock param from the worker config. The only way to get things working is to change the name of the queue the worker is sending jobs to.

Expected behavior
Push new jobs to the queue

Current behavior
Can't push new jobs

Worker class

class Cache::UpdateShopNotificationsWorker
  include Sidekiq::Worker

  sidekiq_options queue: "#{::ActiveJob::Base.queue_name_prefix}#{::ActiveJob::Base.queue_name_delimiter}notification_events_cache",
                  retry: 3,
                  lock:  :until_executed

    def perform(*object_id)
    end
end

Digest entries are empty when running

SidekiqUniqueJobs::Digests.new.entries

[mhenrixon]

How are the jobs pushed to the queue?

[eni9889]

Not sure if this is what you are asking but this:

Cache::UpdateShopNotificationsWorker.perform_async

[mhenrixon]

That's exactly what I was looking for. I just saw ActiveJob in there and needed to know if it is related to ActiveJob or not.

[mhenrixon]

@eni9889 what does your sidekiq/sidekiq-unique-jobs initializer look like?

[eni9889]

SidekiqUniqueJobs.configure do |config|
  config.reaper          = :lua
  config.reaper_count    = 100
  config.reaper_interval = 30
  config.reaper_timeout  = 5
  config.lock_info       = true
end

Happy to provide anything else

[mhenrixon]

@eni9889 few more questions:

1. Which environments does this happen in?
2. Do you have any lock keys in the redis database?

[mhenrixon]

Closing due to inactivity :) See #571 for guidance, there was a lot more work being put into v7 and I suggest to start with v7.0.1