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

sidekiq_options lock conflicts with sidekiq-lock gem lock option #669

Closed
recurator opened this issue Dec 6, 2021 · 1 comment
Closed

Comments

@recurator
Copy link

recurator commented Dec 6, 2021

Hello,

Gem sidekiq-lock and sidekiq-unique-jobs use the same option
sidekiq_options lock: :until_executing
sidekiq_options lock: { timeout: 1000, name: 'project_status_lock' }
which causes an error:
NoMethodError: undefined method to_sym for {:timeout=>10000, :name=>"project_status_lock"}:Hash Did you mean? to_s, to_set /usr/local/bundle/gems/sidekiq-unique-jobs-6.0.13/lib/sidekiq_unique_jobs/options_with_fallback.rb:52:in lock_class'
because sidekiq-unique-jobs does not expect Hash as lock option value which need to be defined as hash in sidekiq-lock.

So far, I have not found a way to make these two gems work together.

@mhenrixon
Copy link
Owner

They should not be used together

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

No branches or pull requests

2 participants