Skip to content

bugfix for weight loading for qwen3-next#21313

Merged
sglang-npu-bot merged 1 commit intosgl-project:mainfrom
McZyWu:bugfix0324
Mar 26, 2026
Merged

bugfix for weight loading for qwen3-next#21313
sglang-npu-bot merged 1 commit intosgl-project:mainfrom
McZyWu:bugfix0324

Conversation

@McZyWu
Copy link
Copy Markdown
Contributor

@McZyWu McZyWu commented Mar 24, 2026

Motivation

previously,
When loading quantization weight such as w8a8, as weight_loader of self.in_proj_qkvz.weight is denoted by @Property, which means it doesn't have a setter method.
when running through this code and sequentially trying to assign another implementation for this method, the error occurs
image

image image

Modifications

as follows.

Accuracy Tests

Benchmarking and Profiling

Checklist

Review Process

  1. Ping Merge Oncalls to start the PR flow. See the PR Merge Process.
  2. Get approvals from CODEOWNERS and other reviewers.
  3. Trigger CI tests with comments or contact authorized users to do so.
    • /tag-run-ci-label, /rerun-failed-ci, /tag-and-rerun-ci
  4. After green CI and required approvals, ask Merge Oncalls to merge.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a bug in the weight loading mechanism for the qwen3-next model. By adjusting the attribute used to assign custom weight loaders, it ensures that the model correctly processes packed checkpoint formats, which is essential for accurate model initialization and operation.

Highlights

  • Weight Loader Attribute Fix: Corrected the attribute used for overriding the weight loader in qwen3-next model's in_proj_qkvz and in_proj_ba layers, changing it from weight.weight_loader to weight._weight_loader to ensure proper handling of packed checkpoint formats.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request fixes a weight loading issue in the Qwen3-next model by updating the attribute name for the weight loader from weight_loader to _weight_loader. While this fixes the bug, I've added a comment regarding the practice of accessing private attributes directly, as it can lead to maintainability issues. Using a public API, if available, would be a more robust solution.

Comment on lines +138 to 143
self.in_proj_qkvz.weight._weight_loader = self._make_packed_weight_loader(
self.in_proj_qkvz
)
self.in_proj_ba.weight.weight_loader = self._make_packed_weight_loader(
self.in_proj_ba.weight._weight_loader = self._make_packed_weight_loader(
self.in_proj_ba
)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Directly assigning to a 'private' attribute like _weight_loader breaks encapsulation and makes the code brittle against dependency updates, as it relies on internal implementation details that could change without notice. A more robust approach is to use a public API if one is available for setting the weight loader. If no such public API exists, this workaround introduces a maintainability risk and it would be beneficial to add a comment explaining the need for this direct access for future reference.

@sglang-npu-bot
Copy link
Copy Markdown
Collaborator

/tag-and-rerun-ci

@sglang-npu-bot
Copy link
Copy Markdown
Collaborator

/rerun-failed-ci

@sglang-npu-bot sglang-npu-bot merged commit 0906e45 into sgl-project:main Mar 26, 2026
140 of 166 checks passed
@yhyang201
Copy link
Copy Markdown
Collaborator

ci 没过就给合了?

@Fridge003
Copy link
Copy Markdown
Collaborator

Seems breaking the qwen3-next accuracy
https://github.com/sgl-project/sglang/actions/runs/23620485893/job/68798399813

Fridge003 added a commit that referenced this pull request Mar 26, 2026
satyamk7054 pushed a commit to satyamk7054/sglang that referenced this pull request Apr 3, 2026
JustinTong0323 pushed a commit to JustinTong0323/sglang that referenced this pull request Apr 7, 2026
yhyang201 pushed a commit to yhyang201/sglang that referenced this pull request Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants