Unsloth solved bug in Mistral Medium 3.5 implementation

<!-- SC_OFF --><div class="md"><p>All ggufs were broken, resulting in bad outputs, especially at long context.</p> <p>Anyway, it is fixed now: <a

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1x6mlby/add_nemotron_super_35_vl_and_nemotron_bolt_74b/"> <img alt="Add Nemotron Super 3.5 VL and Nemotron

<!-- SC_OFF --><div class="md"><p>&#x200b;</p> <p>For anyone running dual AMD GPUs + Vulkan on Windows and suddenly getting crashes with the new Unsloth V3 Qwen3.8-27B quant:</p>

<!-- SC_OFF --><div class="md"><p>Hey everyone, I've been working on getting Multi-Token Prediction (MTP) working with quantized GGUFs for Qwen3-27B and the results are pretty

<!-- SC_OFF --><div class="md"><p>Hey, I don't know if this is a llama.cpp issue or an Unsloth thing, but for whatever reason Mistral Medium 128B at Q4_K_XL seems to go in loops

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1x9yvgw/istadaslabqwen38flashnextgsqrcocodergguf_updated/"> <img

<table> <tr><td> <a href="https://www.reddit.com/r/singularity/comments/1szno73/mistral_medium_35_a_reliability_first_open_source/"> <img alt="Mistral Medium 3.5: A reliability

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1sk6l63/unsloth_minimaxm27gguf_in_broken_udq4_k_xl_avoid/"> <img alt="unsloth - MiniMax-M2.7-GGUF in BROKEN