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

Properly remove eos_token in llama3 tokenizer if requested by user #1477

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

joecummings
Copy link
Contributor

Context

What is the purpose of this PR? Is it to

  • add a new feature
  • fix a bug
  • update tests and/or documentation
  • other (please add here)

Closes #1474

Changelog

  • Adds a test to check if we actually strip eos_token if requested by user
  • Pass in 'None' for truncate if add_eos=False
  • $$$

Test plan

Please make sure to do each of the following if applicable to your PR. (If you're not sure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.)

  • run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
  • add unit tests for any new functionality
  • update docstrings for any new or updated methods or classes
  • run unit tests via pytest tests
  • run recipe tests via pytest tests -m integration_test
  • manually run any new or modified recipes with sufficient proof of correctness
  • include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Example of docstring:


Example in our docs: https://pytorch.org/torchtune/main/tutorials/qat_finetune.html#applying-qat-to-llama3-models

  • I did not change any public API;
  • I have added an example to docs or docstrings;

@joecummings joecummings added bug Something isn't working testing labels Sep 3, 2024
Copy link

pytorch-bot bot commented Sep 3, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1477

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 1e0501e with merge base 71be8ad (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 3, 2024
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 11.11111% with 8 lines in your changes missing coverage. Please review.

Project coverage is 27.01%. Comparing base (71be8ad) to head (1e0501e).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
...s/torchtune/models/llama3/test_llama3_tokenizer.py 14.28% 6 Missing ⚠️
torchtune/models/llama3/_tokenizer.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1477       +/-   ##
===========================================
- Coverage   72.25%   27.01%   -45.25%     
===========================================
  Files         274      274               
  Lines       13278    13306       +28     
===========================================
- Hits         9594     3594     -6000     
- Misses       3684     9712     +6028     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@joecummings joecummings merged commit 26302ac into main Sep 3, 2024
20 checks passed
@joecummings joecummings deleted the fix-1474 branch September 3, 2024 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Llama3 Tokenizer always appends "eos_id" for tokenize_messages
4 participants