DFlash2 capability-gate repro (INTENTIONALLY BROKEN test fixture)

Do not use this for serving. It is a deliberately corrupted draft model that exists only to reproduce a llama.cpp speculative-decoding bug and verify its fix (llama.cpp PR #27342, DFlash2 support).

dflash-27b-q8-selector-key-only.gguf is a byte-identical copy of inco.ai's DFlash v1 draft model for Qwen3.8-27B (MIT) with one metadata key injected: dflash.selector_top_k = 16. No selector tensors were added, so the metadata claims a DFlash2 selector lattice that the decode graph never builds.

What it reproduces

On llama.cpp builds where the host arms the DFlash2 path from the dflash.selector_top_k metadata key alone, run this file as -md with --spec-type draft-dflash against a Qwen3.8-27B target:

  • without the capability gate: no crash and no diagnostic. The v1 graph writes hidden states into t_h_nextn, the host decodes them as candidate token ids, and target verification rejects every draft. Measured on gfx1151/RADV (Vulkan): 0/1556 drafts accepted, 4.77 t/s vs ~11.4 t/s with speculation disabled - a silent 2.4x slowdown with correct output.
  • with the capability gate: a startup warning ("selector metadata but its decode graph does not build the selector lattice") and a clean fallback to the DFlash v1 draft path (162/295 accepted, 25.6 t/s in the same setup).

Rebuild it yourself

The 30-line generator (plus a second script covering the DSV4-backbone load-refusal case) lives on the fork branch dflash2-capgate-repro; the fix itself is the dflash2-capgate branch, commit 0b0f35d0e ("spec : capability-gate the DFlash2 draft path").

Credit: the underlying draft model is by inco.ai (MIT). This repository only adds one metadata key to make the mismatch reproducible.

Downloads last month
-
GGUF
Model size
2B params
Architecture
dflash
Hardware compatibility
Log In to add your hardware

We're not able to determine the quantization variants.

Inference Providers NEW
This model isn't deployed by any Inference Provider. ๐Ÿ™‹ Ask for provider support