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
Ruby version: 2.6.5
Sidekiq / Pro / Enterprise version(s): Sidekiq version 6.1.0, Pro version 5.1.1
Appears that after fixing #4591 we now see a different recurring deprecation warning:
Passing 'exists?' command to redis as is; blind passthrough has been deprecated and will be removed in redis-namespace 2.0 (at /app/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.1.0/lib/sidekiq/launcher.rb:161:in `block (2 levels) in ❤')
While the previous warning could be silenced by explicitly setting Redis.exists_returns_integer = false we are not aware of any similar work around for this warning.
The text was updated successfully, but these errors were encountered:
On Jul 6, 2020, at 01:08, David Backeus ***@***.***> wrote:
Ruby version: 2.6.5
Sidekiq / Pro / Enterprise version(s): Sidekiq version 6.1.0, Pro version 5.1.1
Appears that after fixing #4591 and upgrading to the new Sidekiq version we now see a new recurring deprecation warning:
Passing 'exists?' command to redis as is; blind passthrough has been deprecated and will be removed in redis-namespace 2.0 (at /app/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.1.0/lib/sidekiq/launcher.rb:161:in block (2 levels) in ❤')`
While the previous warning could be silenced by explicitly setting Redis.exists_returns_integer = false we are not aware of any similar work around for this warning.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Ruby version: 2.6.5
Sidekiq / Pro / Enterprise version(s): Sidekiq version 6.1.0, Pro version 5.1.1
Appears that after fixing #4591 we now see a different recurring deprecation warning:
While the previous warning could be silenced by explicitly setting
Redis.exists_returns_integer = false
we are not aware of any similar work around for this warning.The text was updated successfully, but these errors were encountered: