-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Bugfix]Fix MiniCPM's LoRA bug #9286
[Bugfix]Fix MiniCPM's LoRA bug #9286
Conversation
👋 Hi! Thank you for contributing to the vLLM project. 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 do one of these:
🚀 |
@ML-GCN can you try out this PR and see if it fixes the issue for you? |
ok i try now |
not yet |
@ML-GCN could you provibe your lora config? |
{ |
@ML-GCN Please try it again |
i try the first commit i found the output is error by origin params MiniCPM3-4B (https://huggingface.co/openbmb/MiniCPM3-4B) example i input 你好 but the output is |
There was no error reported but the output is error As I mentioned above |
It seems this PR is not responsible for the unsatisfactory result. the main branch:
current PR branch:
|
ok i try again thanks you |
I also tested the generated result using https://huggingface.co/openbmb/MiniCPM3-4B#inference-with-vllm. The result is :
|
yes this is right but you first test the input is 你好 is error result |
@ML-GCN The first test is based on https://github.com/vllm-project/vllm/blob/main/examples/offline_inference.py, possibly due to the lack of the |
@ML-GCN sry, I don't quite understand what you mean. |
o it is my error I read it wrong |
No worries. Does this PR resolve your previous issue? |
yes thanks you very much |
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 pr sove my request thank you
The introduction of GLM-4V is causing LoRA tests to fail on main. Can you fix it in this PR as well? I think you need to update # Used to indicate whether the model is a multimodal model
- self.supports_mm: bool = supports_multimodal(self.model)
+ self.supports_mm = (supports_multimodal(self.model)
+ # In case the model only supports LoRA for
+ # text modules (e.g. ChatGLM)
+ and hasattr(self.model, "get_mm_mapping")) |
@DarkLight1337 I have made the modifications. I don't understand why GLM4V is integrated in this way, it a bit confusing. I think it would be better to use different model script to distinguish between VL and LLM. |
This is because they use the same HF architecture name, so we can't distinguish between them when deciding which vLLM model to load. |
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.
LoRA tests pass should this should be good to merge.
Signed-off-by: Alvant <alvasian@yandex.ru>
Signed-off-by: Amit Garg <mitgarg17495@gmail.com>
Signed-off-by: Sumit Dubey <sumit.dubey2@ibm.com>
Signed-off-by: Maxime Fournioux <55544262+mfournioux@users.noreply.github.com>
FILL IN THE PR DESCRIPTION HERE
FIX #9282
ping @DarkLight1337
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE
PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:
[Bugfix]
for bug fixes.[CI/Build]
for build or continuous integration improvements.[Doc]
for documentation fixes and improvements.[Model]
for adding a new model or improving an existing model. Model name should appear in the title.[Frontend]
For changes on the vLLM frontend (e.g., OpenAI API server,LLM
class, etc.)[Kernel]
for changes affecting CUDA kernels or other compute kernels.[Core]
for changes in the core vLLM logic (e.g.,LLMEngine
,AsyncLLMEngine
,Scheduler
, etc.)[Hardware][Vendor]
for hardware-specific changes. Vendor name should appear in the prefix (e.g.,[Hardware][AMD]
).[Misc]
for PRs that do not fit the above categories. Please use this sparingly.Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:
format.sh
to format your code.docs/source/
if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.
Tensors
require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.torch.libary.opcheck()
to test the function registration and meta-function for any registered ops. Seetests/kernels
for examples.Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with
rfc-required
and might not go through the PR.What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:
action-required
label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.Thank You
Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!