incompatibility with sidekiq-failures

[fwolfst]

Describe the bug
Sorry for cross-posting mhfs/sidekiq-failures#148 - I am not sure what the best way would be.

Update/TL;DR This might be due to #761 (comment) , where timestamps can be nil. However, the situation is still unlucky and could re-occur, since both gems define a global helper with the same name.

sidekiq_unique_jobs has a Locks Web UI in which current locks are rendered. The page also shows when the lock was created, in a safe_relative_time.
sidekiq-failures also implements a safe_relative_times.
See

sidekiq-unique-jobs/lib/sidekiq_unique_jobs/web/helpers.rb

Line 148 in f381562

def safe_relative_time(time)

and
https://github.com/mhfs/sidekiq-failures/blob/2b30cb1c87ce09cfb1758f90cc720ddf50dcb591/lib/sidekiq/failures/web_extension.rb#L9

However, the implementation in sidekiq_unique_jobs seems to be more robust (surviving nil because of a time.to_s in parse_time), resulting in

Now, I am not 100% sure why we have nils here (there is always one weird lock without a timestamp, like here: #761 (comment)), but if I remove sidekiq-failures from the bundle, everything runs fine.

Expected behavior
Time rendered just fine.

Current behavior
See screenshot above, there is a conversion error because a nil timestamp is passed on to the safe_relative_time implementation of sidekiq-failures.

[fwolfst]

Will happily craft a PR if you tell me in which direction you would like a solution to be done.

[mhenrixon]

This is indeed unfortunate, I am guessing it would be better to add sidekiq-unique-jobs last to ensure the safe relative time helper is from this gem (since sometimes the timestamp can be nil).

Apart from that, I have no good ideas at the moment.

[fwolfst]

I guess one way would be to somewhat namespace the helper function (SidekiqUniqueJobs::Webhelpers::safe_relative_times); or rename it ...

[leedrum]

This issue will be resolved by PR-152. But I don't know when it be released