fix: guard MoE branch when quantization_format is None - #2185
fix: guard MoE branch when quantization_format is None#2185andrewwhitecdw wants to merge 1 commit into
Conversation
Signed-off-by: andrewwhitecdw <andrewwhitecdw@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe MoE pre-quantization resmoothing condition now requires a non-null quantization format before excluding ChangesMoE resmoothing
Estimated code review effort: 1 (Trivial) | ~2 minutes Mergeability Score: ⚪ Minimal · up to This localized change prevents a TypeError when MoE export runs with no quantization format and adds regression coverage; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 inconclusive)
✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This PR addresses the following issue in
modelopt/torch/export/unified_export_hf.py: guard MoE branch when quantization_format is None.Changes
modelopt/torch/export/unified_export_hf.py: guard MoE branch when quantization_format is None.Details
Tests
tests/torch/export/test_unified_export_hf.pyContributor guidelines
Per this repo's CONTRIBUTING.md:
Signed-off-bytrailer, DCO).Summary by CodeRabbit