[V1][Core] Add support for V1 Engine on v0.7.3 #376
Merged
Conversation
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
Co-authored-by: didongli182 <[email protected]> Signed-off-by: shen-shanshan <[email protected]>
shen-shanshan
force-pushed
the
v0.7.3-v1
branch
from
9921806 to
a160f09
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it?
Add support for V1 Engine on v0.7.3.
Does this PR introduce any user-facing change?
Find more details at #295.
Plus, due to a bug of
vllm v0.7.3when using modelscope, you should use a lower version ofmodelscope. Find more details at vllm-project/vllm#13807.This can work:
How was this patch tested?
Find more details at #295.