Mikael Henriksson

There is no super to call for lock args method? If you need all your arguments to be in the unique you can just skip defining it. I believe that's...

Sorry about that @ryanbjones that's because this line is wrong https://github.com/mhenrixon/sidekiq-unique-jobs/blob/ca3082b315c964b6d416372d6a911b0ade33b14f/lib/sidekiq_unique_jobs/locksmith.rb#L241 It should be config.timeout not config.ttl. A fix was published as v7.1.5

> LMK if want to hop on a zoom call to look at it I sincerely appreciate that @ryanbjones! So many times I've wished I had someone to help me...

What time zone are you in @ryanbjones? I am out for the day but would be interested in pairing on this tomorrow morning or sometime Friday. I am in CET...

@ryanbjones how about any time from now until 5 hours from now? :) If that doesn't work for you, perhaps sometime tomorrow around the same times would do the trick?...

@ryanbjones if you want to retry the jobs and not loose them I recommend you use ```ruby sidekiq_options lock: :while_executing, on_conflict: { server: :raise } ``` It is normal that...

There seems to have been some trouble with super fetch and unique jobs. I can't debug this because I don't have a sidekiq pro license. What I on the other...

Thank you for the detailed report. Considering what you write last, I suppose there is no way to persuade you to upgrade to v7 just yet?

@michaelegregious I believe you should upgrade sidekiq unique jobs. There was a change in how the args are handled in newer sidekiq versions.

I have an idea, I'll see if I can find a way to finally fix this in the next few days.