add more tokenizer arguments
What does this PR do ?
Add more tokenizer arguments.
:warning: For major changes (either in lines of code or in its impact), please make sure to first share discuss a design-doc with the team.
Contribution process
flowchart LR
A[Pre-checks] --> B[PR Tests]
subgraph Code Review/Approval
C1[Expert Review] --> C2[Final Review]
end
B --> C1
C2 --> D[Merge]
Pre-checks
- [ ] I want this PR in a versioned release and have added the appropriate Milestone (e.g.,
Core 0.8) - [ ] I have added relevant unit tests
- [ ] I have added relevant functional tests
- [ ] I have added proper typing to my code Typing guidelines
- [ ] I have added relevant documentation
- [ ] I have run the autoformatter.sh on my PR
Code review
The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.
For MRs into `main` branch
(Step 1): Add PR label Expert Review
(Step 2): Collect the expert reviewers reviews
- Attach the
Expert Reviewlabel when your PR is ready for review. - GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.
:warning: Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.
(Step 3): Final Review
- Add
Final Reviewlabel - GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.
(Optional Step 4): Cherry-pick into release branch
If this PR also needs to be merged into core_r* release branches, after this PR has been merged, select Cherry-pick to open a new PR into the release branch.
For MRs into `dev` branch
The proposed review process for `dev` branch is under active discussion.MRs are mergable after one approval by either [email protected] or [email protected].
Merging your PR
Any member of core-adlr and core-nemo will be able to merge your PR.
This pull request requires additional validation before any workflows can run on NVIDIA's runners.
Pull request vetters can view their responsibilities here.
Contributors can view more details about this message here.
/ok to test f2d9d56a7183fd7225ec9136f266af711c7eba33
/ok to test 09cf7a381fca519561fc3511c9a689faf57eb6ef
/ok to test 6114de135d6a3c33efd1f959534f4c01bc858dad
/ok to test 8b42c45bc1df8ddfeccd5c36705880fcf2f4c119
As it stands, this PR deletes --tiktoken-special-tokens but doesn't fix all places which refer to the argument, such as this one. I didn't look for others, this was just the first off the top of my head.
All references to the old arg need to be resolved.
/ok to test 95e84a58fd733a9dabcbf8ae15ab7265fd73e0bb
/ok to test 5d9866a27a29ed72312b95a0f43d7a99eb078584
/ok to test 6e2a573221b1997e08c3f793a0e3cc13c51d1cf2
/ok to test 6456fe7ed44deb556e7f97c2b2870d4a363540f9
/ok to test b4f541b79d2e0c703c5ce1181b6d014f9c2b2324
/ok to test dbeccab05179738e6b4ec183d09504b2f85e914d
/ok to test 5306451ebb6982175336a34808ac311132e0474c
/ok to test f1a9c6c5f37a3331499d840d74922f1b59572147
/ok to test 72dee19b1f6648bef2632d1dcc1683300ffa234d