-
Notifications
You must be signed in to change notification settings - Fork 835
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
Sorted metric tags to avoid duplicate prom data with gRPC requests #4006
Conversation
Hi @harshita-meena. Thanks for your PR. I'm waiting for a SeldonIO or todo member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
@harshita-meena Can you look at the linting and test errors? |
Yes sure..taking a look now |
/test integration |
/ok-to-test |
/test this |
@harshita-meena: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
Btw just as a heads up @harshita-meena I had to add a dummy commit as it seems an issue in github was preventing the gh action pipelines to run, but that seems to have done the job |
@harshita-meena it seems there are some failures on the tests, are you able to run these locally? You can do so with |
I was trying to follow the readme here but didn't get to complete the test, ill try your suggestion. thanks! |
I ran the act command locally, but seems to be unrelated to my change, I ran again from main branch, which is failing as well. Do you think it is something related to how my env is setup ? is there a particular python version i should use
|
@harshita-meena it seems the docker image that you are using to run these tests doesn't have the dependencies required for Python CV2 library - you may need to specify explicitly the base image you use to run, alternatively you will have to extend the image you are using to have the cv2 dependencies (ie What is the command that you are using to run these tests? Are you using the |
I am just using simple |
I am guessing this is the image used by default. |
@RafalSkolasinski Added the changes, is there a way I can trigger PR tests ? I did not quite figure out how to work it locally. |
/test integration |
Just unit tests should be sufficient here, however, would you be able to add an unit tests for it? Some model that returns for first request metrics from predict with tags |
Yups definitely, will add it, thanks for an example. |
@harshita-meena: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. |
/test integration |
@harshita-meena: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
/ok-to-test |
The python lint job seemed to fail, could you run |
/ok-to-test |
I have tried these cases before as well but could not recreate it, maybe its still possible. Either way, this small change should cover all such cases :) |
The fmt command got stuck so I used black command first as suggested, now ran isort. |
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.
Nice, thanks for finding the issue and contributing the fix!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RafalSkolasinski The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@RafalSkolasinski Hi! |
Hi, it will come with Seldon Core 1.14 but I don't know the exact release schedule for it. @cliveseldon may know more |
What this PR does / why we need it:
To ensure no duplication of metrics occur in prometheus due to non-unique temp keys dependent on "tags" of custom metrics.
Which issue(s) this PR fixes:
Fixes #3968
Special notes for your reviewer: