-
-
Notifications
You must be signed in to change notification settings - Fork 11k
[Bugfix] Relax lang pin for voxtral #21833
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
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
110fbb5
relax lang pin for voxtral
sanchit-gandhi 9344b34
gemini advice
sanchit-gandhi 1df3084
Update vllm/model_executor/models/voxtral.py
sanchit-gandhi 63e6ead
lint
sanchit-gandhi 9ac2525
up
sanchit-gandhi afb32ce
up
sanchit-gandhi 702f759
requested changes
sanchit-gandhi 2a12816
lint
sanchit-gandhi 27a13c4
var name
sanchit-gandhi cd4e0a1
docstring
sanchit-gandhi 24a9c0e
lint
sanchit-gandhi 4a8ae88
up
sanchit-gandhi 2447fbe
value error
sanchit-gandhi 253027d
lint
sanchit-gandhi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
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.
I am thinking perhaps this should be a
logger.warning_oncecase.Uh oh!
There was an error while loading. Please reload this page.
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 a pretty big assumption that's being made in creating the token ids, e.g. it completely nullifies the model's ability to do multilingual transcription.
Until the TODO is resolved, the best practice when using Whisper is to always specify the language. Otherwise, you end up with undefined behaviour (e.g. audio in Spanish, task set to "transcribe", lang token set to "en" → mis-match with how the model was trained!). This would happen silently if you passed a mix of transcription requests, some with and some without the language field.
Ideally, we would enforce this best practice by throwing an exception if the language is not specified. However, since that's not backwards compatible, a persistent warning is the best we can do. So I'd be in favour of keeping it as
logger.warning!