Skip to content

Comments

Adithyare/sft ultra v3 feb2026#3272

Closed
arendu wants to merge 15 commits intoNVIDIA:mainfrom
arendu:adithyare/sft-ultra-v3-feb2026
Closed

Adithyare/sft ultra v3 feb2026#3272
arendu wants to merge 15 commits intoNVIDIA:mainfrom
arendu:adithyare/sft-ultra-v3-feb2026

Conversation

@arendu
Copy link
Contributor

@arendu arendu commented Feb 5, 2026

What does this PR do ?

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

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]
Loading

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

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

(Step 1): Add PR label Expert Review

(Step 2): Collect the expert reviewers reviews

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ 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

  1. Add Final Review label
  2. 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 eharper@nvidia.com or zijiey@nvidia.com.

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 5, 2026

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.

@arendu arendu marked this pull request as ready for review February 6, 2026 18:58
@arendu arendu requested review from a team as code owners February 6, 2026 18:58
@ko3n1g ko3n1g requested a review from a team February 6, 2026 18:58
@arendu arendu requested a review from a team as a code owner February 13, 2026 19:04
@jaredcasper jaredcasper added the Expert Review Apply this label to indicate that your PR is ready for expert review. label Feb 17, 2026
@Phlip79
Copy link
Member

Phlip79 commented Feb 17, 2026

@arendu please fix conflicts

arendu and others added 8 commits February 18, 2026 10:26
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: Soumye Singhal <soumyes@cw-dfw-cs-001-dc-01.cm.cluster>
Cherry-picked from b3684ec4 "added fix to fix crash"
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
@arendu arendu force-pushed the adithyare/sft-ultra-v3-feb2026 branch from 9ddfa5d to f82168a Compare February 18, 2026 18:46
@arendu arendu requested a review from a team as a code owner February 18, 2026 18:46
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
@jaredcasper
Copy link
Contributor

Is it possible to split this into distinct PRs? Or at the least describe each change. It's hard to review without knowing the whats and whys.

Signed-off-by: adithyare <adithyare@nvidia.com>
Signed-off-by: adithyare <adithyare@nvidia.com>
@arendu
Copy link
Contributor Author

arendu commented Feb 20, 2026

@jaredcasper @Phlip79 I've merged with a more recent main. The changes should only be related to tokenizer building and a logic update regarding EOD tokens.

_set_padded_vocab_size(args, tokenizer)

return tokenizer
elif args.tokenizer_type == 'SFTTokenizer':
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How will this ever run with the case on line 66 present?

@@ -0,0 +1,212 @@
#! /bin/bash
# Copyright (c) 2018-2022, NVIDIA CORPORATION. All rights reserved.
#
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Megatron is not Apache licensed and we don't put the license in each file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we putting these scripts in the repo? Are the generally applicable to any platform?

@guyueh1 guyueh1 self-requested a review February 20, 2026 23:17
@seonjinn seonjinn force-pushed the adithyare/sft-ultra-v3-feb2026 branch from 9a2630e to 2fa3e6f Compare February 20, 2026 23:21
@seonjinn seonjinn force-pushed the adithyare/sft-ultra-v3-feb2026 branch from 2fa3e6f to ee5e581 Compare February 20, 2026 23:35
@arendu
Copy link
Contributor Author

arendu commented Feb 21, 2026

closing in favor of #3526

@arendu arendu closed this Feb 21, 2026
@jaredcasper jaredcasper mentioned this pull request Feb 21, 2026
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

complexity: low Expert Review Apply this label to indicate that your PR is ready for expert review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants