Skip to content
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] add input embedding #11684

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Bryce1010
Copy link
Contributor

@Bryce1010 Bryce1010 commented Jan 2, 2025

adds support for passing prompt_embeds to LLM.generate as

llm.generate({"prompt_embeds": input_embeds}, sampling_params)

or

llm.generate(
    [{"prompt_embeds": input_embeds} for input_embeds in inputs_embeds], sampling_params
)

this enables use cases when only the embedding layer is finetuned, and have the same model backend support multiple custom tuned embedding layers

FIX #416
FIX #8323

Copy link

github-actions bot commented Jan 2, 2025

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@mergify mergify bot added the frontend label Jan 2, 2025
@Bryce1010 Bryce1010 force-pushed the feature/vllm/add-input-embedding branch 4 times, most recently from 662f96c to 0429875 Compare January 2, 2025 11:15
@Bryce1010 Bryce1010 force-pushed the feature/vllm/add-input-embedding branch from 0429875 to 8c7751d Compare January 2, 2025 11:17
@DarkLight1337
Copy link
Member

Thanks for opening this PR, can you explain what this PR is about and how this is related to #11375?

@Bryce1010
Copy link
Contributor Author

Bryce1010 commented Jan 2, 2025

Thanks for opening this PR, can you explain what this PR is about and how this is related to #11375?

@DarkLight1337 Sorry for referencing the incorrect issue number. Please refer to the following issues for
#416
#8323

@DarkLight1337
Copy link
Member

DarkLight1337 commented Jan 2, 2025

There is a related PR #6869, but your solution can sidestep the problem of missing input token IDs (at the cost of being less efficient).

Can you update this PR with the unit tests in #6869 to see whether this solution works correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants