fix: qwen3.6 moe mtp fused expert layout#145
Merged
ISEEKYAN merged 1 commit intoMay 20, 2026
Merged
Conversation
ISEEKYAN
approved these changes
May 20, 2026
ISEEKYAN
approved these changes
May 20, 2026
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.
Problem
When loading Qwen3.6 MoE checkpoints with MTP (Multi-Token Prediction) layers, the bridge raises a KeyError because Qwen3.6 stores MTP expert weights in a
fused/stacked layout(mtp.layers.0.mlp.experts.gate_up_proj with shape [num_experts, ...]), while the existing code only handles the Qwen3.5per-expert layout(mtp.layers.0.mlp.experts.{i}.gate_proj.weight).qwen3.6-35B-A3B

qwen3.5-35B-A3B

Solution
Auto-detect the MTP expert layout at checkpoint load time by checking for the fused key mtp.layers.0.mlp.experts.gate_up_proj in the safetensors index. When the fused layout is detected, map MTP expert parameters to the single stacked HF key and reuse the existing decoder MoE slice/stack logic for both import (slice by expert index from the fused tensor) and export (collect per-expert weights then torch.stack). The Qwen3.5 per-expert MTP path remains unchanged, ensuring backward compatibility.