馃殌 The feature, motivation and pitch
GGUF models with non-standard quant type prefixes like Unsloth Dynamic 2.0 (UD-) cannot be loaded via repo_id:quant_type format.
vllm serve unsloth/Qwen3-0.6B-GGUF:UD-IQ1_S --tokenizer Qwen/Qwen3-0.6B
huggingface_hub.errors.HFValidationError: Repo id must use alphanumeric chars, '-', '_' or '.'. The name cannot start or end with '-' or '.' and the maximum length is 96: 'unsloth/Qwen3-0.6B-GGUF:UD-IQ1_S'.
Currently, is_remote_gguf() validates quant types against GGMLQuantizationType members and a hardcoded suffix list (_M, _S, _L, etc.). Prefixed types like UD-IQ1_S are rejected, and the model string falls through to HuggingFace Hub as a plain repo ID.
Since quant_type is only used for glob file matching (*-{quant_type}.gguf) and not for actual quantization logic (read from GGUF binary headers), accepting non-standard prefixed names is safe.
Alternatives
No response
Additional context
No response
Before submitting a new issue...
馃殌 The feature, motivation and pitch
GGUF models with non-standard quant type prefixes like Unsloth Dynamic 2.0 (UD-) cannot be loaded via repo_id:quant_type format.
Currently, is_remote_gguf() validates quant types against GGMLQuantizationType members and a hardcoded suffix list (_M, _S, _L, etc.). Prefixed types like
UD-IQ1_Sare rejected, and the model string falls through to HuggingFace Hub as a plain repo ID.Since quant_type is only used for glob file matching (*-{quant_type}.gguf) and not for actual quantization logic (read from GGUF binary headers), accepting non-standard prefixed names is safe.
Alternatives
No response
Additional context
No response
Before submitting a new issue...