-
Notifications
You must be signed in to change notification settings - Fork 581
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
Simplify manage to autodetect task+framework if possible. #122
Conversation
Could you also quickly change the inference api Actions checks to run in pull_request, not only PR? They don't seem to trigger with latest unless I do manually.
Also, |
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.
Looks awesome, thanks!
api-inference-community/manage.py
Outdated
info = HfApi().model_info(model_id) | ||
task = info.pipeline_tag | ||
framework = None | ||
frameworks = { |
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.
Nit: please sort frameworks
alphabetically :)
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.
Ahaah is that really that important ? :D
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.
That's why it's a nit :)
api-inference-community/manage.py
Outdated
framework = tag | ||
else: | ||
raise Exception( | ||
"This model seems to implement 2 frameworks, we cannot infer" |
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.
Just a comment: I wonder if this can become an issue later on with models such as sentence-transformers
that work fine in both transformers and sentence-transformers.
modelInfo
currently does not return the library, but I think it should. It's already there, we just need to add it to the returned modelInfo. I can send a PR for that next week.
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.
@julien-c is implementing library_name
or something similar, so we should be able to switch to that and avoid this edge case.
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.
This is already done now :)
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.
You can do info.library_name
No description provided.