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
Can you please extend the info on upgrading to 4.x or acknowledge my guess below. The changelog mentions 100% breaking changes for version 4.0.0. I guess the change is that you no longer simply put sidekiq_options :unique => true but have to explicitly decide on the way you want your uniqueness to be enforced as per the Locking section. As far as I understood :while_executing matches the behavior of the old true config. So the easy upgrade path would be making sure that there are no queued jobs and switching to the appropriate locking strategy.
Another guess is that 3.0.15 and 4.0.1-4.0.6 got yanked to promote the use of the new explicit API (to preserve data integrity) and not a CVE or other security related thing.
I don't want to be harsh on you (sorry if it sounded that way), but I learnt to love explicitness recently ;-)
Thank you very much for making and maintaining this gem, much appreciated!
Someone has an idea why this could happen?
The text was updated successfully, but these errors were encountered: