-
Notifications
You must be signed in to change notification settings - Fork 39
fix(redis): resolved pool instrumentation to use instance instead of prototype #2092
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please update redis to 5.9.0 as part of this PR and then run against 5.8.3 and 5.9.0 in pkg json? Ty
bc1759c to
c1bd72a
Compare
…prototype The instrumentation for pool was returning the prototype instead of the instance, which is wrong and will broke private-field access.
52140cf to
f04aaf5
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will address the double calls in a separate JIRA for redis 5.9.0.
These appear as soon as you install redis 5.9.0 - the changes in the instrumentation are not responsible for that.



The instrumentation for pool was returning the prototype instead of the instance, which is wrong and will broke private-field access.
Redis v5.9.0 introduced change, which modified how createClientPool initializes the client, causing private fields like #isOpen to become inaccessible when wrapped by our tracer.