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

Silence Redis deprecation warnings in worker logs #2275

Merged
merged 1 commit into from Jun 16, 2020
Merged

Conversation

duncanjbrown
Copy link
Contributor

The warning:

`Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?`
returns a boolean, you should use it instead. To opt-in to the new
behavior now you can set Redis.exists_returns_integer =  true. To
disable this message and keep the current (boolean) behaviour of
'exists' you can set `Redis.exists_returns_integer = false`, but this
option will be removed in 5.0.

The call comes from Sidekiq, which will fix this with v6.1. Until then,
silence it.

sidekiq/sidekiq#4591

The error:

`Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?`
returns a boolean, you should use it instead. To opt-in to the new
behavior now you can set Redis.exists_returns_integer =  true. To
disable this message and keep the current (boolean) behaviour of
'exists' you can set `Redis.exists_returns_integer = false`, but this
option will be removed in 5.0.

The call comes from Sidekiq, which will fix this with v6.1. Until then,
silence it.
@tvararu tvararu temporarily deployed to apply-for-te-redis-warn-bnmy2s June 15, 2020 13:53 Inactive
@tvararu tvararu added the Core Shared issue between candidate/vendor/support/API label Jun 16, 2020
@duncanjbrown duncanjbrown merged commit aefd118 into master Jun 16, 2020
@duncanjbrown duncanjbrown deleted the redis-warning branch June 16, 2020 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Shared issue between candidate/vendor/support/API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants