Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove deprecated/broken OptionsWithFallback#unique_type #435

Merged
merged 2 commits into from
Mar 21, 2020

Conversation

zvkemp
Copy link
Contributor

@zvkemp zvkemp commented Oct 17, 2019

When enqueuing a job, the client middleware continues to viewsidekiq_options unique: :until_executed as valid, and inserts a lock for the job. However, the Locksmith does not look at the deprecated unique_type method (only the LOCK 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 well edit: 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 of lock, it seems best to remove it entirely.

Copy link
Owner

@mhenrixon mhenrixon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, it should totally be removed for v7! Thank you for your contribution 👍

@mhenrixon
Copy link
Owner

Thanks a bunch for the contribution! I will backport the fix for v6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants