-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
[Misc] unify variable for LLM instance #20996
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
[Misc] unify variable for LLM instance #20996
Conversation
👋 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 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 🚀 |
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.
Summary of Changes
Hello @andyxning, 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 focuses on improving code readability and consistency by standardizing the variable name used for vllm.LLM
instances. The change involves renaming variables from model
or vllm_model
to llm
throughout the codebase, including documentation, examples, and test files. This refactoring aims to make the code more intuitive and easier to understand for developers.
Highlights
- Code Readability & Consistency: Standardized the variable name for
vllm.LLM
instances frommodel
(orvllm_model
) tollm
across various parts of the codebase, including documentation, examples, and test 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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request consistently renames the LLM
instance variable from model
to llm
across documentation, examples, and tests, which improves code clarity. I found one instance in docs/features/lora.md
that needs to be updated to use the new llm
variable.
508cac3
to
d1978c3
Compare
Done. |
d708b55
to
cc16303
Compare
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 clean up!
Head branch was pushed to by a user without write access
cc16303
to
6bb5c9b
Compare
6bb5c9b
to
e96128e
Compare
83ace72
to
cb4f32a
Compare
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 this PR, I agree this is a good clarification.
My initial review was not complete, I just wanted to request my changes before merging might have happened.
I have a few more comments.
864f553
to
3c4a138
Compare
@hmellor can you review again? Tests pass now |
@DarkLight1337 @hmellor All ci are finally green. PTAL. |
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 making those changes, a couple of nits and an issue with a third party method which we shouldn't change
3c4a138
to
d83e6a6
Compare
All done. |
d83e6a6
to
6b8c116
Compare
Seems that tpu-v1-test failure is a flake. @DarkLight1337 @hmellor can you help confirm this? |
Yes it's a known issue. Retrying |
@DarkLight1337 @hmellor the ci is all green now. PTAL. |
Can you fix the merge conflicts? |
This pull request has merge conflicts that must be resolved before it can be |
6b8c116
to
fc96fd5
Compare
9a1aae1
to
a8921a2
Compare
Signed-off-by: Andy Xie <andy.xning@gmail.com>
a8921a2
to
25c486b
Compare
@DarkLight1337 @hmellor ci is green now. PTAL. |
@andyxning It looks like there are some left over tests that needs to be updated https://github.com/vllm-project/vllm/blob/main/tests/models/language/generation/test_gemma.py#L17-L26. I'm seeing that test failing after my recent rebase https://buildkite.com/vllm/ci/builds/24547#01982fc1-9f0c-4a14-9419-0ff0ea5c50f8/209-8333
|
Essential Elements of an Effective PR Description Checklist
supported_models.md
andexamples
for a new model.Purpose
Unify LLM instance name to
llm
instead ofmodel
to make it more clear. Improve code readibility.Test Plan
NA
Test Result
NA
(Optional) Documentation Update