llama.cpp decision runner (D41): reproducible build pipeline + smoke-tested release binary

Aberta
  • Algo errado?
#9 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
cmake, git, rust
Domínio
backend-api-design, build-system, devops

Direção de pesquisa

Start with forks/llama.cpp/build.sh, then read forks/llama.cpp/README.md, docs/FORK_LLAMA_SERVER.md, and the just build-llama-fork recipe. Run the documented CPU build from a fresh clone and record its output; completion requires a provenance manifest and a smoke-tested llama-server that returns a per-choice distribution from a real GGUF at /v1/decision.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Context

D41 established branch-only tracking of a llama.cpp decision-inference fork: base `thecodacus/llama.cpp` @ `parallel-decision` (tree-mode `POST /v1/decision`), plus fast-LoRA kernels when a CUDA port exists (RESEARCH §28; 1Cat-vLLM recorded as V100/SM70 informatics reference only — serving path stays llama.cpp static binary, no Python at runtime).

The skeleton landed on main (c2fec9a) but the tracked pipeline never produced a binary:

  • `forks/llama.cpp/build.sh` defaulted to `github.com/opencodifier/llama.cpp` — 404 (fork never promoted); real base is `thecodacus/llama.cpp`
  • CMake flags were invented names (`LLAMA_SERVER`, `LLAMA_EXAMPLES`, `GGML_STRIP`) that silently defaulted everything ON — correct names are `LLAMA_BUILD_*`
  • `LLAMA_BUILD_TOOLS=OFF` silently removes the `llama-server` target (server lives under `tools/server/`)
  • Historical ad129b0/38de7eb builds were ad hoc, never through this script — nothing reproducible to release
  • No branch: skeleton work went straight to main

Scope (this ticket, branch `fork/llama-decision-2026-10`)

Working worktree: `/nas/Temp/repos/OpenCodifier-fork` (separate from main working tree).

  • `build.sh`: correct repo URL, correct `LLAMA_BUILD_*` flags, `BACKEND=cpu|cuda|vulkan`, provenance manifest (`BUILD-INFO.txt`: base/final commit, backend, host, UTC)
  • `forks/llama.cpp/.gitignore` so `build/`, clone, and logs never pollute commits
  • Working compiled binary: `BACKEND=cpu` build completes; binary produced at `forks/llama.cpp/build/bin/llama-server`
  • Smoke test: built binary serves `POST /v1/decision` against a real GGUF and returns a per-choice distribution; commands + output recorded in the ticket
  • Docs aligned: `forks/llama.cpp/README.md` + `docs/FORK_LLAMA_SERVER.md` real repo URL; `just build-llama-fork` recipe verified against the new script
  • `BACKEND=cuda` path documented for T5500/V100 builds (build executed there later)
  • PR through the DevOps pipeline (CI = `.gitforge.yml` gates)

Explicitly out of scope (linked, other sessions)

  • Fast-LoRA kernel A/B (woct0rdho CUDA port does not exist yet — §28) → follow-up after this lands
  • Fork CI smoke-build job → follow-up once the build recipe is stable here
  • D42 e2e test fix, main-tree CI gates, E1-G eval wrap → main-session work, untouched by this branch

Acceptance

A fresh clone of this branch + `cd forks/llama.cpp && BACKEND=cpu ./build.sh` yields a working `llama-server` whose `/v1/decision` answers a real request, with the build provenance in `BUILD-INFO.txt`.

Linguagem predominante
Rust
Estrelas
1
Forks
0
Merge médio
13h 10min
PRs com merge (30d)
12

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de aliasfoxkde/OpenCodifier

Todas as issues de aliasfoxkde/OpenCodifier

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.