bump emerging optimizers to v0.3.0

[FDecaYed]

mirror of #5320

• I, the PR author, have personally reviewed every line of this PR.

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 @NVIDIA/mcore-oncall.

Issue tracking

For PRs from open-source community contributors:

• New features: a linked issue is required. Please open a feature request and reference it here before submitting the PR.
• Small updates (bug fixes, minor improvements): a linked issue is recommended and will accelerate the PR review process.

Linked issue:

Contribution process

Pre-checks

• 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

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

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

1. When your PR is ready, click Ready for Review.
2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
   • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

[copy-pr-bot]

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.

[github-actions]

This PR has been automatically converted to draft because all PRs must start as drafts.

When you are ready for review, click Ready for Review to begin the review process. This will:

1. Add the oncall reviewer (optional reviewer)
2. Add required review teams based on your changes

See the contribution guide for more details.

[FDecaYed]

/ok to test aebd169

[FDecaYed]

/ok to test 48232cb

[FDecaYed]

/ok to test 9b57159

[janEbert]

Unrelated to this PR, but regarding lines 383–402 (can't select them on GitHub):

Can't we use AdaptiveMuon.__init__ instead of TensorParallelMuon.__init__ to initialize the TensorParallelAdaptiveMuon optimizer? That way, we use more external code and don't need to keep updating. We can even refactor the shared setup code between the two classes.

I'll build I built that change on top of this PR.

[Phlip79]

/claude fix

[svcnvidia-nemo-ci]

🛠️ Claude fix commit 954665779cfc (attempt 1)

⚠️ This explanation is AI-generated and may be inaccurate; the exact commit is authoritative.

What changed
Resolved the pyproject.toml + uv.lock merge conflict as the union of both sides: nemo-run advanced to main's rev e3935393, emerging＿optimizers kept the PR's v0.3.0, main's deep-gemm entry retained in uv.lock's no-pypi-wheels group. Verified no markers remain, both files parse as TOML, and pins match their locked stanzas. Nothing staged or committed; MERGE＿HEAD intact. The 26 unit failures were left unchanged as unsupported.

Files changed by Claude

• pyproject.toml
• uv.lock

Why
Main and the PR each bumped a different one of two adjacent lines in (tool.uv.sources), so git could not split the hunk: main moved nemo-run, the PR moved emerging＿optimizers. Either side alone would revert the other's bump, and the rest of uv.lock had auto-merged to that union. CI failures are environment drift (missing FLA, removed torch.＿C attrs, grad-dtype errors), not text defects; no lint failures. uv.lock was hand-resolved from pins already in the PR, as no container was available.

DCO
@FDecaYed, please fix any DCO failures on your commits before merge. DCO does not block this workflow.

View exact commit

Sanitized and posted by svcnvidia-nemo-ci.

[svcnvidia-nemo-ci]

/ok to test 9546657

[svcnvidia-nemo-ci]

❌ Claude fix stopped because exact-SHA CI did not complete in time. View exact-SHA CI.

[Phlip79]

/ok to test 4098200