-
Notifications
You must be signed in to change notification settings - Fork 236
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
Exception ERR unknown command 'exists?'
in 3.1.0
#345
Comments
In 3.1.0 it tries to use `exists?` instead of `exists`, but `exists?` does not exist: sidekiq-scheduler/sidekiq-scheduler#345
@barrucadu I'll take a look tonight |
Which version of redis are you using? Ok, I see and it looks like that it's 4.1.4 |
@barrucadu The problem happens because your project I'll be able to fix this on sidekiq-scheduler side, but that will require a major bump since we have to upgrade some dependecies and with that also drop support for ruby 2.2, 2.3 and 2.4 because those dependencies droped support for this ruby versions. (ruby 2.4 already reached EOL so I think that's not a problem) I'll revert #335 which means the warning will come back to 3.x and will only be resolved on 4.0 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@barrucadu I've merged #370, can you test on your end with the |
Using Any suggestions? |
@ustincameron According to the Sidekiq readme (which is tracking sidekiq 7), Sidekiq 7.x requires Redis 6.2 or later. |
@t27duck My apologies for the typo, currently running The schedule is being loaded and the logs are showing the jobs are firing appropriately, but unable to see the recurring jobs via the web view. |
Hmmm... something seems off then. The app I have (where the reoccurring jobs tab works fine) has the exact same versions as you listed... minus Ruby which is 3.1.3. |
@ustincameron can you provide a stack trace? And if possible, a sample app? |
Hello, I think the change introduced in #335 isn't quite right, as in my app the
r.exists?
case is always getting called, even though it's not supported by redis gem I'm using:This is making the worker crash on start-up:
This could be an issue in sidekiq or the redis gem but, since it's surfacing in this gem, I'm reporting it here.
For now I'll downgrade the gem to version 3.0.1.
The text was updated successfully, but these errors were encountered: