-
Notifications
You must be signed in to change notification settings - Fork 67
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
Usage of nested-asyncio in the Python client #774
Comments
thanks @blublinsky do you want to describe to the community what are your thoughts of the modification/improvement you want to propose here? |
In the current implementation Model registry client is using |
yes, here: model-registry/clients/python/src/model_registry/_client.py Lines 84 to 87 in 550e294
Interesting, thanks for the context
At this point I'm also wondering as well if other REST client generators for python which directly produce sync rest calls 🤔 but your proposal SGTM too, I'm going to raise the attention to this at the next KF Model Registry biweekly (next one is Monday Feb 17th) |
Thanks, @tarilabs, please keep me posted on the progression and let me know when I can create a PR. We need this functionality yesterday and for now just patching implementation locally, but would like to have it as part of the project. |
ie I'm trying to understand if you are suggesting to change only |
this is always encouraged, but especially if you have a local patch even more encouraged! |
just the client.
So basically it just replacing async-runner implementation |
indeed feel free to raise as PR, that is always encouraged |
thanks @tarilabs |
the pr is here #802 |
much appreciated @blublinsky thank you |
Describe the bug
The current implementation of the model registry client uses nested async (registry/blob/main/clients/python/src/model_registry/_client.py#L130, which works fine for standalone client usage, but fails when running inside Ray or any other framework using uviloop.
To Reproduce
Here is a simple failing Ray sample:
Expected behavior
This should of produce:
but instead it produces the following exception:
Additional context
I am willing to provide PR
The text was updated successfully, but these errors were encountered: