Repository navigation
[gRPC] Expose multimodal flag + tokenizer metadata via get_init_info #25170
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
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Oops, something went wrong.
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.
The logic for
eos_token_idshas two issues:hf_eos_token_idis a single integer (common in many models),sorted()will raise aTypeErroras integers are not iterable.or []will treat a token ID of0as falsy and return an empty list instead of[0].It's safer to explicitly handle the integer case and check for
None.References
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.
Thanks for the careful read. Both concerns are technically defused by an upstream invariant, but you're right that the diff doesn't show that — so I've pushed a defensive rewrite in 83c2f89 that makes the safety locally obvious.
Details on the original code, for the record:
Bare
int→TypeError—model_config.hf_eos_token_idis populated byModelConfig._get_hf_eos_token_id, which normalizes HF'sint | list[int] | Noneinto aSet[int](line 1307 wraps a bare int with{eos_ids}, line 1309 substitutesset()forNone). By the timesorted()sees it, it's always a set.or []drops0—orwas operating on the set, not a scalar.bool({0}) is True, so{0} or [] == {0}andsorted({0}) == [0]. The falsy-zero footgun is real for scalarintfields but not for sets.That said, the producer's type annotation is
Optional[Set[int]], which advertises aNonereturn the function never actually produces. The handshake shouldn't depend on a cross-file invariant the type system doesn't enforce, so the new commit coerces inline:isinstance(int)runs first so token ID0survives (isinstance(0, int) is True,[0] or [] == [0]). Same behavior today, robust against future refactors.