You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
context"#RegularWorker"doit"unlock is never called for a worker not using unique extension"dojid=RegularWorker.perform_async('test')item=Sidekiq::Queue.new(QUEUE).find_job(jid).itemexpect(@middleware).not_toreceive(:unlock)@middleware.call(RegularWorker.new,item,QUEUE)dotrueendendend
The text was updated successfully, but these errors were encountered:
I've been updating the tests for the run_lock PR and noticed this behaviour.
For example AfterYield Worker is defined with unique: false
https://github.com/mhenrixon/sidekiq-unique-jobs/blob/master/spec%2Fsupport%2Fafter_yield_worker.rb
But there are tests which still expect it to unlock: https://github.com/mhenrixon/sidekiq-unique-jobs/blob/master/spec%2Flib%2Fserver%2Fmiddleware_spec.rb#L90
In fact this fails:
The text was updated successfully, but these errors were encountered: