• Stefy Lanza (nextime / spora )'s avatar
    a component_quantization value nobody understands must not vanish · 08df8843
    Stefy Lanza (nextime / spora ) authored
    The map takes 4bit / 8bit / 2bit or a .gguf path. Anything else was skipped
    without a word -- and one unusable entry empties the mapping, which takes the
    global load_in_4bit with it, so the component loads from the base repo at full
    precision while the operator believes it comes from the file they named.
    
    LTX-2.5 named a bf16 Gemma-4 12B for its text_encoder. The quantization config
    came back None, the 12B loaded unquantized, and every generation ended with
    the card full: 23.53 GiB of 23.56 GiB in use, unable to allocate 30 MiB, on a
    model whose own measured footprint is 14.45 GB. Four strategies and about an
    hour of 20-minute attempts, all of them really the same missing line.
    
    Now it says so, and names component_models -- the key that does what such a
    value was meant to do.
    Co-Authored-By: 's avatarClaude Opus 5 <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_014T3rZnLhydX9QqUcfBbqLu
    08df8843
test_component_quantization_modes.py 1.8 KB