Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Slurm: support Qwen3.8-capable vLLM runtimes

クローズ
  • 何か問題がありますか？
#1,085 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
58/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
docker, python
領域
ai-infra-agents, devops

調査の方向性

Start with the version gate and rejection logic in packages/data-designer-slurm/src/data_designer/slurm/serving/resolver.py, then inspect how selected vLLM images are imported and validated. Reproduce the preflight rejection and the checkpoint architecture check described in the issue. Done means a qualified Qwen-capable runtime is supported, incompatible versions still produce specific errors, and generation/collection smoke coverage and supported-image documentation are added.

索引モデルが issue の本文から書いたものです。

説明

enhancement
Priority Level

High (Major improvement)

Problem

DD Slurm's vLLM runtime gate blocks migration of an existing Qwen/Qwen3.8-Flash-Next workload. The resolver currently admits only 0.21.x and 0.22.x. Our existing model-specific serving artifact reports 0.1.dev20073+g8e685d198 and is rejected at preflight; switching to the supported official 0.22 image also cannot load this checkpoint.

Reproduction and confirmed results

Tested the Slurm integration at 9ba05f5451f99df65dbf3835916139e23ad523e4, with hosted-provider PR #1080 applied at 4be9ff26249f09f751cff22234f9f84e9f4e3841. The runtime gate is unchanged by that PR.

  1. Native DD Slurm image import/inspection succeeded for vllm/vllm-openai:v0.22.0, pinned to OCI digest sha256:0fec7ec5f3e6bc168e54899935fb0557da908a4832a1dbc88e2debcf2f889416. Inspection correctly reported vLLM 0.22.0.

  2. Inside that image on a CPU allocation (aarch64, Transformers 5.9.0), load the same checkpoint's config:

    from transformers import AutoConfig

AutoConfig.from_pretrained(
    "/models/Qwen3.8-Flash-Next",
    local_files_only=True,
    trust_remote_code=False,
)

    Result: ValueError: The checkpoint you are trying to load has model type qwen4_exp but Transformers does not recognize this architecture.

    Its config declares Qwen4ExpForConditionalGeneration with no auto_map; the image's vLLM registry also lacks that architecture. This check required no GPU allocation or weight loading.

  3. The existing runtime validator rejects both the model-specific development version and 0.30.0, reporting that only 0.21.x and 0.22.x are supported.

Proposed path

Qualify a Qwen-capable upstream runtime and extend the tested release coverage, including a small generation/collection smoke with the existing checkpoint and inference settings. The upstream Qwen recipe currently specifies stable vLLM >=0.30.0 or nightly; those runtimes have not yet been qualified with DD Slurm.

Document the supported path for model-specific/nightly images and preserve the specific version rejection in preflight errors. If an opt-in compatibility path is needed, bind it to the inspected image digest and explicit qualification rather than accepting every version or rewriting its reported version.

Investigation and context
  • Runtime gate and rejection.
  • Image import packages the selected upstream runtime into SQSH; it does not add missing model implementations. Rebuilding the same 0.22 image therefore does not resolve this gap.
  • Hosted-only CPU generation and collection passed under #1080. Mixed-provider SQL qualification remains blocked by this independent local-serving compatibility issue; no end-to-end success is claimed.
  • Related: #969 (versioned serving images), #866 (serving resolution), #1079 (hosted providers).
  • Reviewed existing issues and found no duplicate covering this model/runtime gap.
Checklist
  • I've reviewed existing issues and the documentation.
  • This is a design proposal, not a "please build this" request.
主要言語
Python
スター
2.4k
フォーク
241
平均マージ
1日 19分
マージ済み PR（30日）
84

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

NVIDIA-NeMo/DataDesigner のほかの issue

NVIDIA-NeMo/DataDesigner の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。