[dev] fix(moe): Fix DSA spec and rope. - #3402
Merged
Merged
Conversation
6 tasks
Contributor
Author
|
/ok to test 96495c5 |
Contributor
Author
|
/ok to test 19c5f45 |
hxbai
reviewed
Feb 13, 2026
| ), | ||
| ) | ||
|
|
||
| # Adjust for RMS norm. |
Contributor
There was a problem hiding this comment.
Could you leave a comment on why layernorm_linear cannot be used here? Thanks.
Contributor
Author
There was a problem hiding this comment.
Yes. I add some comments below. Does it look good?
yuzhongw-nvidia
force-pushed
the
yuzhongw/fix_dsa_spec_dev
branch
from
February 25, 2026 06:51
19c5f45 to
be5648f
Compare
Contributor
Author
|
/ok to test be5648f |
yuzhongw-nvidia
force-pushed
the
yuzhongw/fix_dsa_spec_dev
branch
from
February 25, 2026 08:09
be5648f to
35d6110
Compare
Contributor
Author
|
/ok to test 35d6110 |
yanring
self-requested a review
February 26, 2026 04:40
Contributor
Author
|
/ok to test f935a3b |
fix uv.lock
…ndexer Update attention.py Update transformer.py Update test_rope.py rename multi_latent_attention -> mla_rotary_interleaved
yuzhongw-nvidia
force-pushed
the
yuzhongw/fix_dsa_spec_dev
branch
from
March 5, 2026 09:29
7324f19 to
311b567
Compare
Contributor
Author
|
/ok to test 311b567 |
Contributor
|
/ok to test 3307414 |
ko3n1g
approved these changes
Mar 6, 2026
Contributor
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/22753432406 |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Mar 6, 2026
Contributor
Author
|
/ok to test f362a99 |
hxbai
enabled auto-merge
March 6, 2026 09:31
Contributor
Author
|
/ok to test 484fd1a |
Contributor
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/22763776708 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do ?
PR for main: #3026, #3403
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
Core 0.8)Code review
The following process is enforced via the CODEOWNERS file for changes into
megatron/core. For changes outside ofmegatron/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
Expert Reviewlabel when your PR is ready for review.Final Review might get declined if these requirements are not fulfilled.
(Step 3): Final Review
Final Reviewlabel(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, selectCherry-pickto 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.comorzijiey@nvidia.com.Merging your PR
Any member of core-adlr and
core-nemowill be able to merge your PR.