Skip to content

chore: ⬆️ Update ggml-org/llama.cpp to 74ce15741b420b8d6f12e720398458b576c51c2c - #11329

Open
localai-bot wants to merge 2 commits into
mudler:masterfrom
ci-forks:update/LLAMA_VERSION
Open

chore: ⬆️ Update ggml-org/llama.cpp to 74ce15741b420b8d6f12e720398458b576c51c2c#11329
localai-bot wants to merge 2 commits into
mudler:masterfrom
ci-forks:update/LLAMA_VERSION

Conversation

@localai-bot

@localai-bot localai-bot commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from 32b8387 to e91a9ac Compare August 4, 2026 20:34
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to fe2adf0e722f30f5295fdec8a0f1dc788f7498bc chore: ⬆️ Update ggml-org/llama.cpp to 4308a4f035791f58ae111f56c39dac598bf476be Aug 4, 2026
@mudler

mudler commented Aug 4, 2026

Copy link
Copy Markdown
Owner

@localai-org-maint-bot fix this

@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator

Fixed and pushed in 3b1d05109. The llama.cpp gRPC wrapper now calls the new eval_llama_cmpl_schema signature in both completion paths while preserving the legacy params_from_json_cmpl fallback. The completed lint, Linux/Apple tests, llama.cpp smoke, Darwin backend build, and current CPU/Vulkan backend jobs are green; the remaining backend matrix jobs are still running.

@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from 3b1d051 to d2624d3 Compare August 5, 2026 22:25
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to 4308a4f035791f58ae111f56c39dac598bf476be chore: ⬆️ Update ggml-org/llama.cpp to f9e832c10e9444cb168ddcb579cc62c154f3068b Aug 5, 2026
@mudler

mudler commented Aug 6, 2026

Copy link
Copy Markdown
Owner

@localai-org-maint-bot check again failures

@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from d2624d3 to 0156836 Compare August 6, 2026 22:35
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to f9e832c10e9444cb168ddcb579cc62c154f3068b chore: ⬆️ Update ggml-org/llama.cpp to 15586e2d7165570fb3aa7c26e0d442e289ef69de Aug 6, 2026
@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from 0156836 to f9da4a5 Compare August 7, 2026 20:38
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to 15586e2d7165570fb3aa7c26e0d442e289ef69de chore: ⬆️ Update ggml-org/llama.cpp to 3653e6d6d547ec763317d9ecd0ace334a7e21359 Aug 7, 2026
@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from f9da4a5 to 969df23 Compare August 8, 2026 20:09
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to 3653e6d6d547ec763317d9ecd0ace334a7e21359 chore: ⬆️ Update ggml-org/llama.cpp to 687e7789271ec1276e3470f158428e11a4f80b6f Aug 8, 2026
@mudler

mudler commented Aug 8, 2026

Copy link
Copy Markdown
Owner

@localai-org-maint-bot fix CI issues

@localai-bot
localai-bot force-pushed the update/LLAMA_VERSION branch from 969df23 to 64fadeb Compare August 9, 2026 20:09
@localai-bot localai-bot changed the title chore: ⬆️ Update ggml-org/llama.cpp to 687e7789271ec1276e3470f158428e11a4f80b6f chore: ⬆️ Update ggml-org/llama.cpp to 74ce15741b420b8d6f12e720398458b576c51c2c Aug 9, 2026
mudler and others added 2 commits August 9, 2026 22:02
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Split the modern server-schema calls from the legacy fallback so each receives the arguments required by its pinned llama.cpp API.

Assisted-by: Codex:gpt-5
@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator

Picked this back up and pushed a53e703c8 on top of current master. The pinned llama.cpp revision removed slot_n_ctx from eval_llama_cmpl_schema but the legacy fallback still requires it, so the modern and legacy calls now have separate preprocessor branches with their exact signatures. I verified both call sites against upstream 74ce1574 and git diff --check; the long backend builds are left to the newly triggered CI run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants