shipfeedAI news, curated daily

00:32:36 CET
21 MAY00:32:36shipfeed
pull to refreshlast sync
Just in — 30 new
§ local-llm · storyline

llama.cpp b9141

llama.cpp b9141 adds a continue_final_message flag to its server API for vLLM compatibility, aliasing the existing prefill_assistant path and enforcing mutual exclusion with add_generation_prompt.

May 14 · · primary fetch1 sourceupdated May 14 ·

server, webui: accept continue_final_message flag for vLLM API compat (#23012) server, webui: accept continue_final_message flag for vLLM API compat Add the continue_final_message body flag from the vLLM and transformers API. When set together with add_generation_prompt false, it triggers the existing prefill_assistant code path, regardless of the server side opt.prefill_assistant option. Mutual exclusion with add_generation_prompt true is enforced, matching vLLM behavior. WebUI sends continue_final_message and add_generation_prompt false on the Continue button, with the matching opt in option on the chat service.

Pure API alignment, no change to the prefill logic itself. Paves the way for the upcoming per-template prefill plumbing in common/chat. test: add coverage for continue_final_message vLLM compat flag Two cases on top of the existing assistant prefill coverage. First, continue_final_message true with add_generation_prompt false produces the same rendered prompt as the prefill_assistant heuristic, proving the new flag is a correct alias of the existing path. Second, both flags set to true is rejected with HTTP 400, matching the vLLM/transformers mutual exclusion contract…

read full article on github.com
§ sources1 publication · timeline below
  1. github.comllama.cpp b9141primary