THUDM / THUDM/slime

[Bug] qwen 35 megatron bridge install error

Open
#1,711 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
8.5k
Forks
1.3k
Avg merge
5h 36m
Merged PRs (30d)
22

Description

Bug Description

https://github.com/coding-famer/Megatron-Bridge-slime/tree/qwen35
from megatron.bridge.models.conversion.peft_bridge import AdapterWeightConversionTask, MegatronPeftBridge
but you dont have this src/megatron/bridge/models/conversion/peft_bridge.py

ModuleNotFoundError: No module named 'megatron.bridge.models.qwen_vl.qwen25_vl_provider'
ModuleNotFoundError: No module named 'megatron.bridge.models.mla_provider

Steps to Reproduce

no

Expected Behavior

no

Actual Behavior

no

Environment
  • slime version:
  • Python version:
  • PyTorch version:
  • CUDA/ROCm version:
  • GPU type and count:
  • OS:
  • SGLang version (if relevant):
  • Megatron-LM version (if relevant):
Logs

Additional Context

No response

Pre-submission Checklist
  • I have read the CONTRIBUTING.md and understand the collaboration scope.
  • I have read the documentation and my issue is not addressed there.
  • I have searched for existing issues and this is not a duplicate.
  • I have provided a minimal, reproducible example.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the qwen35 branch linked in the report with the installed source, especially src/megatron/bridge/models/conversion/peft_bridge.py and the qwen_vl.qwen25_vl_provider and mla_provider import paths. Reproduce the installation and trace which package version or branch provides the missing modules. Done means the reported imports resolve without ModuleNotFoundError.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.