LockInfo attempts to explain why a lock exists. It provides information like worker class, unique arguments and…

The previous version of sidekiq-unique-jobs didn’t really provide enough details about a lock to be helpful. It just listed all keys without any context. Version 7 provides a more detailed extension to Sidekiq::Web

Sometimes it is desireable to allow a job to run 2 or 3 times with the same unique arguments. The lock_limit configuration enables this.

One of the problems with this gem was that sometimes old locks stayed forever and the only way to fix it was to nuke the entire redis database. This feature prevents that by continuously running a cleanup of orphaned locks.

Some settings are not compatible with each other and this has been a source of confusion to people. The documentation isn’t particularly good at highlighting this so I decided to provide a way to easily test your worker configuration.

Being able to debug the lua scripts proved to be paramout while building out version 7. Since logging slows down the processing it is turned off by default.

The changelog provides a sort of audit log for unique jobs. It adds an entry for each event that could prove useful for debugging.

The changelog is automatically cleaned up based on how many items are allowed.

My name is Mikael and I am a recovering 10x developer. I am sober since one year, two months and three days.

I’ve maintained the gem sidekiq-unique-jobs for a long time. Since July 26, 2012. A lot of work has gone into the gem. It has been quite a journey and I appreciate the challenge.