Repository navigation
issue 601 -> capability unification - #622
Merged
Lazarus-931 merged 2 commits intoSep 25, 2026
Merged
Lazarus-931 merged 2 commits into
Lazarus-931 merged 2 commits into
Conversation
Collaborator
|
LGMT |
lucasnewman
approved these changes
Sep 25, 2026
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
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.
this patches further edge cases as a followup for #617, a much generalized solution like consistent query/classification as well as fixing a audio distinction such that asr models remain stt and tts models remain text to speech in classification.
which means they are no longer incorrectly labeled as general Audio merely because their metadata mentions speech/audio.
this was extensively tested with live hf api, 20 focused tests, representative and combined filters in models page