If a job is deleted from the enqueued list, it's still unique and new jobs can't be added. about sidekiq-unique-jobs HOT 8 CLOSED

I faced the same problem

from sidekiq-unique-jobs.

Same here

from sidekiq-unique-jobs.

any updates on this pls? Have an issue while testing the worker - cant start unique worker second time even if the first one is removed from queue...perhaps this issue is connected to this

from sidekiq-unique-jobs.

Interesting, I wonder if it has to do with the arguments. I'll write some test cases

from sidekiq-unique-jobs.

I explored this a little bit and it appears that lock is not cleared after deleting from web UI, because obviously it does not run any middewares, like it does after finishing the job or if the job is failed.

from sidekiq-unique-jobs.

Isn't this what sidekiq_unique_ext.rb is supposed to handle? I noticed that the file isn't required anywhere except for its spec. Not sure why that is.

from sidekiq-unique-jobs.

So we obviously need to require the file when sidekiq/api is required or sidekiq/web for that matter. If anyone have any knowledge in how to extend sidekiq functionality somehow now is the time to tell :)

from sidekiq-unique-jobs.

This has been closed for a while.

from sidekiq-unique-jobs.