remove deprecated/broken OptionsWithFallback#unique_type #435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When enqueuing a job, the client middleware continues to view
sidekiq_options unique: :until_executed
as valid, and inserts a lock for the job. However, the Locksmith does not look at the deprecatedunique_type
method (only theLOCK
key), so when running the lock.lua script, the conditional that should unlock upon completion (if lock == "until_expired" and ttl then ...
) is never executed.Discovered on version 6.0.15 (
earlier 6.0.x releases have this issue as welledit: appears to have been introduced in 6.0.15), and though 7.0.0.beta2 has been considerably refactored, it still appears to be an issue.Given that
unique
was deprecated as of 6.0 in favor oflock
, it seems best to remove it entirely.