Mikael Henriksson
Mikael Henriksson
https://github.com/mhenrixon/sidekiq-unique-jobs/issues/571 `v7.0.1` is highly recommended.
@privorka which conflict resolution did you have configured before?
Great suggestions @tahanson ! I'm so glad I've awaited some feedback on this
Please checkout v7.1.26 https://github.com/mhenrixon/sidekiq-unique-jobs/releases/tag/v7.1.26 as it has quite a few fixes for until and while executing
Also, if you are still having trouble: https://github.com/mhenrixon/sidekiq-unique-jobs/releases/tag/v7.1.27 (especially if you are using redis-namespace).
Must be, I'll see if I can replicate this in a test.
@ArturT worker configuration? Just need the `sidekiq_options` really.
@ArturT I tried to replicate the problem either in the rails console or in tests.
It was good you had me have a look at this because I discovered that I unintentionally created a breaking change that was fixed in 7.1.1 just now.
@ArturT I can't think of a single thing. I've checked both the connection pool gem and the sidekiq gem and this behavior seems like a mystery to me.