-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
[Core] Remove prompt string from engine core data structures #17214
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
By design, V1 engine core deals only with token ids. EngineCoreRequest contained an optional string prompt field, but we always set it to None before sending to the engine. It's used only by the output processor to set the prompt back in output messages returned to the user. It's best to remove it from EngineCoreRequest to make this separation clear/explicit. Signed-off-by: Nick Hill <nhill@redhat.com>
|
👋 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 🚀 |
| def __init__( | ||
| self, | ||
| request_id: str, | ||
| prompt: Optional[str], |
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 is always None anyhow
|
|
||
| req_id: str | ||
| prompt_token_ids: list[int] | ||
| prompt: Optional[str] |
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 is always None anyhow
Signed-off-by: Nick Hill <nhill@redhat.com>
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 streamlining this! LGTM once tests are green
Signed-off-by: Nick Hill <nhill@redhat.com>
Signed-off-by: Nick Hill <nhill@redhat.com>
…oject#17214) Signed-off-by: Nick Hill <nhill@redhat.com>
…oject#17214) Signed-off-by: Nick Hill <nhill@redhat.com>
…oject#17214) Signed-off-by: Nick Hill <nhill@redhat.com> Signed-off-by: Agata Dobrzyniewicz <adobrzyniewicz@habana.ai>
…oject#17214) Signed-off-by: Nick Hill <nhill@redhat.com> Signed-off-by: Mu Huai <tianbowen.tbw@antgroup.com>
…oject#17214) Signed-off-by: Nick Hill <nhill@redhat.com> Signed-off-by: Yuqi Zhang <yuqizhang@google.com>
By design, V1 engine core deals only with token ids.
EngineCoreRequestcontained an optional string prompt field, but we always set it toNonebefore sending to the engine. It's used only by the output processor to set the prompt back in output messages returned to the user.It's best to remove it from EngineCoreRequest to make this separation clear/explicit.