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-namespace endless warnings #40
Comments
Hey @RanAbram, thanks for your kind words, I appreciate it 🙏 I have a bit of a trouble with my laptop, but I will try to update redis-namespace this week and release a new Docker image. Thanks for rising the issue 💚 |
Hola @RanAbram, finally I get my laptop situation resolved. Feel free to use the latest image (0.1.15-2) with updated docker pull strech/sidekiq-prometheus-exporter:0.1.15-2 |
Thanks man, will try it later on :) |
@Strech This seems to still be happening in the latest version of the image (
|
Hey @scottcrossen, can you show me gems + ruby version in your |
@Strech Sorry just saw this!
(which does have v1.8.1 of redis-namespace)
@RanAbram do you still have these errors after upgrading to the latest image? |
@scottcrossen Sorry for a long silence, I will take a look this week, was a bit busy 😵 |
Thanks to everyone for re-rising this issue @scottcrossen @RanAbram. The problem was with a As the result, I've updated not only You can pull updated image with tag
UPD: The code is not pushed yet as the Helm package, but will be by tomorrow ✌️ |
Hi @Strech,
First of all, thanks for this great project, really appreciate your work here!
Second, we started to use the out of the box docker you provided, but on our production env
we are seeing endless amount of warnings about that
Redis#exists(key) will return an Integer in redis-rb 4.3
.As part of my investigation, it seems that
redis-namespace
gem is the root cause for those warnings andit seems that it was already fixed. Is there any chance to update the version of
redis-namepspace
to the latest one 1.8.1?Sources:
Our logs with the warnings:
The text was updated successfully, but these errors were encountered: