Bug fix for illegal memory access error caused when running medusa lora and plain loras in parallel.#525
Merged
ajtejankar merged 2 commits intomainfrom Jun 26, 2024
Merged
Conversation
The error is caused by incorrect indices passed to the BGMV kernel
tgaddair
approved these changes
Jun 25, 2024
Contributor
tgaddair
left a comment
There was a problem hiding this comment.
Nice! Is there a small unit test we can add to validate this as well?
Contributor
Author
Yup, added a small unit test and refactored the code a bit so that it's clearer. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The error is caused when forwarding through the BGMV kernel during the decode stage and when there are multiple lora adapters. The reason is the discrepancy between the list of lora weight pointers and indices into them. This pull request fixes this. I used the following script to test that everything is working properly.
Run it with parameters
--num-workers 10 --num-requests 100 --seed 123