-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix number transformation from json files in heartbeat #13348
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
The bug is identical to the following: |
@alvarolobato / @andrewvc do you have any spare time reviewing me? |
Sure, I'll take a look. Jenkins, test this please |
Pinging @elastic/uptime |
Looking good! Two things before we can merge this:
Thanks for the great work! Once we have those in we can merge this. |
@andrewvc Done! |
Jenkins, test this please |
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.
LGTM
Prior to this patch heartbeat could not check JSON responses for numeric values correctly because they were incorrectly being cast to the wrong type for comparison. (cherry picked from commit fb62c66)
Prior to this patch heartbeat could not check JSON responses for numeric values correctly because they were incorrectly being cast to the wrong type for comparison. (cherry picked from commit fb62c66)
Thanks for the contribution! It will most likely go out in our 7.4.0 release. See the 7.4 backport here: #13465 |
elastic#13465) Prior to this patch heartbeat could not check JSON responses for numeric values correctly because they were incorrectly being cast to the wrong type for comparison. (cherry picked from commit 90b7aa7)
I noticed a bug when trying to use
equals
check at heartbeat.I would like it to be merged and to get a fixed version soon.
I'm not a GO developer, so if you'd like to change what I wrote, feel free.