Skip to content

Conversation

@princepride
Copy link
Contributor

@princepride princepride commented Jun 12, 2025

Essential Elements of an Effective PR Description Checklist

Purpose

Test Plan

  • Test command:
    vllm serve mistralai/Magistral-Small-2506 --tokenizer_mode mistral --config_format mistral --load_format mistral --tool-call-parser mistral --enable-auto-tool-choice
Screenshot 2025-06-12 at 4 47 35 PM Screenshot 2025-06-12 at 4 47 59 PM

Test Result

Screenshot 2025-06-12 at 4 48 45 PM

Signed-off-by: 汪志鹏 <wangzhipeng628@gmail.com>
@github-actions
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @princepride, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses issue #19495 by updating the required version of the mistral_common dependency. This change ensures compatibility or leverages new features/fixes available in version 1.6.0 of the library.

Highlights

  • Dependency Update: Updated the mistral_common[opencv] dependency version from >= 1.5.4 to >= 1.6.0 in both the common and test requirements files.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added the ci/build label Jun 12, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the mistral_common[opencv] dependency from version >=1.5.4 to >=1.6.0 in requirements/common.txt and requirements/test.in. I've suggested considering a more precise version pin (e.g., ==1.6.0) for mistral_common to enhance stability.

Copy link
Collaborator

@houseroad houseroad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution. Could you paste the test plan (such as verifying the issue is fixed)?

Signed-off-by: 汪志鹏 <wangzhipeng628@gmail.com>
@aarnphm aarnphm changed the title fix #19495 [Fix] bump mistral common to support magistral Jun 12, 2025
@princepride
Copy link
Contributor Author

Screenshot 2025-06-12 at 4 47 35 PM Screenshot 2025-06-12 at 4 47 59 PM Screenshot 2025-06-12 at 4 48 45 PM

@princepride princepride requested a review from houseroad June 12, 2025 08:51
Copy link
Collaborator

@aarnphm aarnphm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, this makes sense to me, but can you update the description of the PR with the image you provided, following the default PR format?

Thanks.

@princepride princepride requested a review from aarnphm June 12, 2025 09:01
@aarnphm aarnphm enabled auto-merge (squash) June 12, 2025 09:06
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 12, 2025
Copy link

@gaby gaby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, currently unable to use Magistral because of this

@princepride
Copy link
Contributor Author


[2025-06-12T09:46:20Z] ==================================== ERRORS ====================================
--
  | [2025-06-12T09:46:20Z] _____ ERROR collecting tests/models/multimodal/generation/test_pixtral.py ______
  | [2025-06-12T09:46:20Z] models/multimodal/generation/test_pixtral.py:114: in <module>
  | [2025-06-12T09:46:20Z]     _create_engine_inputs(IMG_URLS[:1]),
  | [2025-06-12T09:46:20Z] models/multimodal/generation/test_pixtral.py:73: in _create_engine_inputs
  | [2025-06-12T09:46:20Z]     tokenizer = MistralTokenizer.from_model("pixtral")
  | [2025-06-12T09:46:20Z] /usr/local/lib/python3.12/dist-packages/mistral_common/tokens/tokenizers/mistral.py:189: in from_model
  | [2025-06-12T09:46:20Z]     return tokenizer_cls()
  | [2025-06-12T09:46:20Z] /usr/local/lib/python3.12/dist-packages/mistral_common/tokens/tokenizers/mistral.py:362: in <lambda>
  | [2025-06-12T09:46:20Z]     "pixtral": lambda: MistralTokenizer.v3(is_tekken=True, is_mm=True),
  | [2025-06-12T09:46:20Z] /usr/local/lib/python3.12/dist-packages/mistral_common/tokens/tokenizers/mistral.py:142: in v3
  | [2025-06-12T09:46:20Z]     return cls.from_file(str(cls._data_path() / tokenizer_name), mode=ValidationMode.test)
  | [2025-06-12T09:46:20Z] /usr/local/lib/python3.12/dist-packages/mistral_common/tokens/tokenizers/mistral.py:239: in from_file
  | [2025-06-12T09:46:20Z]     raise TokenizerException(f"Unrecognized tokenizer file: {tokenizer_filename}")
  | [2025-06-12T09:46:20Z] E   mistral_common.exceptions.TokenizerException: Unrecognized tokenizer file: /usr/local/lib/python3.12/dist-packages/mistral_common/data/tekken_240911.json

@houseroad Some unit test failed. What should I do?

@gaby
Copy link

gaby commented Jun 12, 2025

@princepride The test_pixtral.py file probable needs to be updated.

Here's the PR for v11 from mistral_common https://github.com/mistralai/mistral-common/pull/91/files

@princepride
Copy link
Contributor Author

@princepride The test_pixtral.py file probable needs to be updated.

Here's the PR for v11 from mistral_common https://github.com/mistralai/mistral-common/pull/91/files

That's weird. I checked this PR, it sames the pixtral tokenizer mapping didn't make any change, and I checked the source code, the tekken_240911.json file under the mistral_common/data folder: https://github.com/mistralai/mistral-common/tree/main/src/mistral_common/data,

@princepride
Copy link
Contributor Author

@houseroad 😓 seems it's a bug in mistral_common==1.6.0: mistralai/mistral-common#94

@gaby
Copy link

gaby commented Jun 12, 2025

@princepride Hopefully they fix it quickly

@patrickvonplaten
Copy link
Collaborator

Nice catch with the data folder - that's indeed needed for the tests. Fixing now. Should be done in 1h

gguf >= 0.13.0
importlib_metadata; python_version < '3.10'
mistral_common[opencv] >= 1.5.4
mistral_common[opencv] >= 1.6.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
mistral_common[opencv] >= 1.6.0
mistral_common[opencv] >= 1.6.2

@houseroad
Copy link
Collaborator

Let's update the version and re-trigger the tests :-)

@patrickvonplaten
Copy link
Collaborator

Sorry about that - we should have read the uv docs better before switching 😅

Signed-off-by: 汪志鹏 <wangzhipeng628@gmail.com>
auto-merge was automatically disabled June 12, 2025 15:28

Head branch was pushed to by a user without write access

@aarnphm aarnphm removed the ready ONLY add when PR is ready to merge/full CI is needed label Jun 12, 2025
@aarnphm aarnphm added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 12, 2025
@gemini-code-assist
Copy link
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@princepride
Copy link
Contributor Author

@houseroad Hmm, that's weird, the Unit test failed, it seems not a problem of my code.

@houseroad
Copy link
Collaborator

The failed test shouldn't be related.

@houseroad houseroad enabled auto-merge (squash) June 13, 2025 03:21
@vllm-bot vllm-bot merged commit ace5cda into vllm-project:main Jun 13, 2025
94 of 96 checks passed
@gemini-code-assist
Copy link
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@gaby
Copy link

gaby commented Jun 15, 2025

@patrickvonplaten @patrickvonplaten Even with this Magistral doesn't work with vLLM. It goes into a thinking loop.

Similar issue reported here: https://huggingface.co/mistralai/Magistral-Small-2506/discussions/15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/build ready ONLY add when PR is ready to merge/full CI is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Latest Mistral Model requires v11 from mistral_common

6 participants