You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We appreciate your work on the sidekiq-unique-jobs gem. We've encountered an issue while using version 8.0.2.
We are using :
Rails 7.0.5
Sidekiq 7.1.2
Redis 7.0.11
ruby 3.2.2
Describe the bug
During normal operations, we noticed a deprecation warning in our logs related to the use of the rpoplpush command in Redis. Here's the relevant log output:
2023-06-16 12:16:34.050556985 +0200 CEST [worker-1] [sidekiq#5788]
Redis has deprecated the "rpoplpush" command, called at
["/app/vendor/bundle/ruby/3.2.0/gems/sidekiq-unique-jobs-8.0.2/lib/sidekiq_unique_jobs/locksmith.rb:315:in 'rpoplpush'"]
Expected behavior
The warning suggests that rpoplpush has been deprecated. According to the Redis documentation (as of the time this issue was created), it is recommended to use the rpop and lpush commands in sequence or use the blpop and rpush commands.
As of Redis version 6.2.0, this command is regarded as deprecated.
It can be replaced by LMOVE with the RIGHT and LEFT arguments when migrating or writing new code.
Hello, Team,
We appreciate your work on the sidekiq-unique-jobs gem. We've encountered an issue while using version 8.0.2.
We are using :
Describe the bug
During normal operations, we noticed a deprecation warning in our logs related to the use of the rpoplpush command in Redis. Here's the relevant log output:
Since Sidekiq 7.1.0:
Expected behavior
The warning suggests that rpoplpush has been deprecated. According to the Redis documentation (as of the time this issue was created), it is recommended to use the rpop and lpush commands in sequence or use the blpop and rpush commands.
As of Redis version 6.2.0, this command is regarded as deprecated.
It can be replaced by LMOVE with the RIGHT and LEFT arguments when migrating or writing new code.
https://redis.io/commands/rpoplpush/
The text was updated successfully, but these errors were encountered: