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

Redis#exists(key) Warning from redis 4.2.0 #286

Closed
majksner opened this issue Jun 10, 2020 · 10 comments · Fixed by #288
Closed

Redis#exists(key) Warning from redis 4.2.0 #286

majksner opened this issue Jun 10, 2020 · 10 comments · Fixed by #288

Comments

@majksner
Copy link

sidekiq/sidekiq#4591

Changes needed:

https://github.com/ondrejbartas/sidekiq-cron/blob/master/lib/sidekiq/cron/job.rb#L464

- conn.zadd(job_enqueued_key, time.to_f.to_s, formated_last_time(time).to_s) unless conn.exists(job_enqueued_key)
+ conn.zadd(job_enqueued_key, time.to_f.to_s, formated_last_time(time).to_s) unless conn.exists?(job_enqueued_key)

https://github.com/ondrejbartas/sidekiq-cron/blob/master/lib/sidekiq/cron/job.rb#L543

- out = conn.exists redis_key name
+ out = conn.exists? redis_key name
@jankeesvw
Copy link

I'm also seeing this deprecation warning, can I do anything to fix this?

@majksner
Copy link
Author

majksner commented Jul 1, 2020

@jankeesvw Until it's fixed you can fork library and change what I have above and point your Gemfile to your github repository.

@MikeRogers0
Copy link
Contributor

MikeRogers0 commented Jul 1, 2020

@jankeesvw I've just made a PR, you can update your Gemfile to track my bugfix branch if you'd like (Though as a warning, CI on the PR isn't passing):

gem 'sidekiq-cron', github: 'MikeRogers0/sidekiq-cron', branch: 'bug/fix-redis-warning'

:)

@cbaudouinjr
Copy link

Any updates on getting this PR to pass CI/get merged in? I can help if needed!

@botularius
Copy link

Any news on this?

@hebbo
Copy link

hebbo commented Jan 26, 2021

Keeping an eye here also in search of a fix. Thanks!

@MikeRogers0
Copy link
Contributor

MikeRogers0 commented Jan 26, 2021

I sent an email to @ondrejbartas to see if he's ok & will merge my PR with the fix to this, I'm guessing he might have notifications turned off & hasn't seen this thread yet.

@h0jeZvgoxFepBQ2C
Copy link

Ping @ondrejbartas

@tleish
Copy link

tleish commented Feb 12, 2022

Why was this ticket closed when it's still an issue with the released gem?

@olegykz
Copy link
Contributor

olegykz commented Apr 7, 2022

@tleish I've created #318 to finally get rid of the deprecation warning

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

Successfully merging a pull request may close this issue.

9 participants