-
Notifications
You must be signed in to change notification settings - Fork 31.4k
[chameleon] fix num image token check #36918
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
Conversation
|
Hi 👋, thank you for opening this pull request! The pull request is converted to draft by default. When it is ready for review, please click the |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
ArthurZucker
left a comment
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.
LGTM thanks for fixing
|
Processor tests failing are all Mistral3, need a read-token which I just added. Not sure yet if the bot has access to Mistral3 though |
* [chameleon] fix num image token check * embed after merging image token * skip this also * mistral require_read_token
* [chameleon] fix num image token check * embed after merging image token * skip this also * mistral require_read_token
* [chameleon] fix num image token check * embed after merging image token * skip this also * mistral require_read_token
What does this PR do?
As per title, reported by Harry as it affects vLLM internal tests. The error was never caught because apparently Chameleon tested only text inputs w/o images
Added tests for
Vision2Seqand made sure all green