-
Notifications
You must be signed in to change notification settings - Fork 184
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
Feature/queue metrics #860
Feature/queue metrics #860
Conversation
…er into feature/queue-metrics
…er into feature/queue-metrics
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.
Hey @alvarorsant,
Thanks for adding these changes!
Besides some naming conventions on the metrics, and some of the changes introduced in the tests, I think this looks great! We're almost there.
Hey @alvarorsant , Just noticed some of the comments were marked as resolved, but I can't see any newer commits. Is there anything else that needs to be pushed before the next review cycle? |
Hi @adriangonz, Thanks in advance for you dedication. |
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 one! Thanks for applying those changes and thanks a lot for your massive effort on this PR. I know there have been a few back and forths, so thanks for your patience! This is a great contribution to have in MLServer! 🚀
Once the tests and linter are green, this should be ready to go ahead. Let me know if you need any help with those. 👍
BTW on the CI checks, linter seems to be complaining about a few unused imports. You can run this locally by calling
Similarly, tests seem to fail due to a import error as well. You can kick these off locally by calling
|
how can I solve the last errors of linter? |
Hey @alvarorsant , It may be that you're running an older version of some of the artefacts. Could you try to rebase from |
Done! |
If I do make lint locally, it works. Check if something has changed after generationgit |
Hey @alvarorsant , It seems one of the rebases missed the latest auto-generated gRPC stubs from I've pushed them manually to this branch now, so hopefully linter should pass in CI now. |
Hey @alvarorsant , It seems some of the runtime tests get stuck while running. I tried running these locally, and the errors I get look along the following lines:
You should be able to run these locally with the command below (note that you can also do
|
It's already corrected |
runtimes/mlflow/tests/rest/conftest.py:19: error: The return type of a generator function should be "Generator" or one of its supertypes [misc] I already used this method without a problem |
Hi @adriangonz , |
Hi @adriangonz, |
Hey @alvarorsant , It seems some tests have failed due to an issue that's now fixed in |
Done , I've already updated it |
Hey @alvarorsant , It seems during your last merge from Given this PR has already been opened for a while, to keep things moving, I've pushed the new ones from |
All seems good now! Thanks a lot for your effort on this one @alvarorsant 👍 Regarding releases, this will likely come out on the |
Thanks @adriangonz |
Fix in tests, duplicate prometheus registry error