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
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.