-
Notifications
You must be signed in to change notification settings - Fork 231
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
Increment start_pos by encoded size in generate #1462
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchchat/1462
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit e238a46 with merge base 654bb03 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Hi @nlpfollower! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
I'd love to look into this a bit more Can you share a repro? |
Certainly. I run the chat feature for Llama3.1-8B-Instruct with a command looking like this: And I've tried the following prompting [main branch]:
With the suggested change, it appears the model starts to reply accurately [fork branch]:
For convenience, I've made a separate branch on my fork with logs that show how we're referencing the kv cache through the |
Hi, seems like the size of
encoded
should contribute tostart_pos
on each turn. Without this change, I'm getting inconsistent generations, as the model looks up kv from the middle of the cache, rather than the end. This also feels like a natural place to incrementstart_pos
, since right after we also increment by the size of generatedtoken_tensor
.