From 7aaebc0e00f9a55e8a1405a45637654b2f864630 Mon Sep 17 00:00:00 2001 From: Daniel Han Date: Sun, 30 Aug 2026 11:20:57 +0000 Subject: [PATCH] unsloth: pin ggml-org#27941 (qwen4exp follow-up fixes) We ship Qwen3.8-Flash-Next GGUFs and the qwen4exp path in the nightlies still has the defects this fixes. The fixes exist, in two places, and neither of them currently reaches a user. #27941 is a strict superset of our own unslothai#143: same four files, nine more lines in llama-memory-hybrid-idx.cpp, plus a llama-kv-cache.cpp change #143 does not carry. Both are mine. Pinning the upstream one means one copy to maintain and a clean retirement once a base tag contains it; #143 is closed as superseded. Scope is narrow. llama_memory_hybrid_idx is reached from exactly one model, so nothing outside qwen4exp can regress on this pin, and the defects are backend independent, which is what explains the reporter who saw the same failure on Vulkan where the ROCm-specific issues do not apply. Open and MERGEABLE upstream at the pinned commit. Drop this entry once a base tag carries the work. --- scripts/unsloth/pr-set.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/unsloth/pr-set.json b/scripts/unsloth/pr-set.json index 9bcd34d88da..83d5514aa54 100644 --- a/scripts/unsloth/pr-set.json +++ b/scripts/unsloth/pr-set.json @@ -24,6 +24,7 @@ "https://github.com/unslothai/llama.cpp/pull/91/commits/c86ed269986f2dced6325c5c58bda966a2e2ead1", "https://github.com/unslothai/llama.cpp/pull/95/commits/3db8cb5b2e9bf291057b9f19960e8601a162da81", "https://github.com/ggml-org/llama.cpp/pull/27754/commits/f30bed88717059d8a4728864c88f8abad8d329a0", - "https://github.com/unslothai/llama.cpp/pull/137/commits/4e1865e34ec5f6ca39403215c89129c13731be70" + "https://github.com/unslothai/llama.cpp/pull/137/commits/4e1865e34ec5f6ca39403215c89129c13731be70", + "https://github.com/ggml-org/llama.cpp/pull/27941/commits/8161d117fed5c37303081ba95bb63a415fe041ac" ] }