[inference] Kill the ability to override a model's task #1199
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julien-c
requested review from
SBrandeis,
coyotte508 and
hanouticelina
as code owners
coyotte508
approved these changes
Feb 12, 2025
|
(i think the CI failure is transient/unrelated) |
SBrandeis
approved these changes
Feb 12, 2025
julien-c
added a commit
that referenced
this pull request
Feb 13, 2025
|
Follow-up in #1201 |
julien-c
added a commit
that referenced
this pull request
Feb 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Excerpt from internal convo:
I was wondering, do you know by any chance if, in the old hf-inference-api, the ability to override the pipeline when calling the API between a feature-extraction and a sentence-similarity model, is still used?
I am thinking to kill this feature from the client libraries (it's simpler to always assume 1 model === 1 task) and i figured you might know if we still use this anywhere