Repository navigation
0.3.0
Changes since the last Release
Changed
-
Update llama.cpp to v0.4.0 (from v0.3.0); whisper.cpp and stable-diffusion.cpp unchanged. Two upstream signature changes, both caught at compile time.
llm_ffn_exps_block_regex(i)becamellm_ffn_block_regex(i, ffn_regex)when upstream generalised the MoE offload helpers to cover dense FFN tensors too (--n-cpu-ffn);--n-cpu-moenow passesLLM_FFN_EXPS_REGEXexplicitly. The siblingllm_add_n_cpu_ffn_overrides()was not adopted: it parks the pattern strings in a function-localstatic std::listthat grows on every call, which is fine for a process that loads one model and wrong for a library whoseload_*entrypoints can be called repeatedly; chimera already owns the storage inModelExtras.mtmd_helper_bitmap_init_from_file()gained a fourthmtmd_helper_init_optargument carrying the video decode parameters; the two call sites passmtmd_helper_init_opt_default(), since--video-fps/--video-timestamp-ms/--ffmpeg-dirreach the decoder throughmtmd_helper_video_init()on the explicit--videopath, not through image loading.Runtime-visible without a code change:
LLAMA_SESSION_VERSION9 -> 10 andLLAMA_STATE_SEQ_VERSION2 -> 3, so slot state written by an earlier chimera (--slot-save-path) is rejected on load. Not wrapped:llama_model_params::lazy_mode(on-demand tensor reads) and upstream's new--n-cpu-ffn.
Fixed
- An embedding input longer than the context aborted the process.
Embedder::embed()tokenized withadd_specialand handed the result straight tollama_decode, but the encoder path assertsGGML_ASSERT(cparams.n_ubatch >= n_tokens && "encoder requires n_ubatch >= n_tokens")-- anabort()inside llama.cpp, not a return code, so there was nothing downstream to turn into a clean exit.chimera embedon any text past the model's context died this way, and so didchimera index ingestat its default settings: the chunkers clampchunk_tokenstoEmbedder::n_ctx(), which counts content tokens only, soadd_specialthen adds the model's[CLS]/[SEP]on top and a full-width chunk arrives over the line. Withbge-small-en-- whose 512-token training context is also the default chunk window -- that is the first full chunk of the first file, so ingesting a README with a default-configured collection never worked.-c/--ctx-sizewas no escape;n_ubatchis not derived from it.embed()now clamps tomin(n_ctx, n_ubatch), the same clamp rather than fail policy the two guards inchimera_serve.cppalready applied on the server paths, and re-seats the trailing separator token after the resize --clsandlastpooling both read the ends of the sequence, so dropping it would change what those two pool over. The first truncation perEmbedderwarns on stderr; later ones are silent, since ingest drives thousands of chunks through one instance. Thechunk_by_tokensdocs claimed the opposite invariant ("chunks always fit throughembed(text)without truncation") and have been corrected to describe the special-token headroom rather than promise it.
Added
-
scripts/rat.py("run artifact tests"), a smoke-test runner for build artifacts.make testtests the tree you just built; nothing tested the binary CI produces, which is the one that gets released.rat.pychecks it before release:--bintakes a bare executable (a downloaded CI artifact or a local build),--asseta local archive or URL, andrat.py install --cudaresolves a GitHub release (default/releases/latest), picks the asset from the backend plus the host ----cudaon Linux ischimera-<version>-linux-x86_64-cuda.tar.gz-- and unpacks the binary intobuild/rat/;rat.py test test-allthen drives that binary's CLI across embeddings, transcription, generation, the vector store and image generation, andrunis install + test + clean in one command. Two things the suite knows that a hand-run CLI does not:--gpu-layersis not optional (chimera's llama-side subcommands default to 0, so a GPU release tested without it would pass every case while measuring nothing but the CPU path), and every case passes--db/--cache-dbexplicitly or points$CHIMERA_DBinto its own output directory, so a smoke run never creates collections in the user's real store. Its entire footprint is one directory,build/rat/(the binary,downloads/for the archives it came from,out/for everything a run produces;--build-dir, defaulting to the Makefile'sBUILD_DIR) -- already gitignored, already whatmake cleansweeps -- exceptmodels/, which stays at the root shared withmake testrather than re-downloading tens of GiB after every clean. Ported from cyllama's wheel tester, with the virtualenv machinery dropped -- a static binary has no interpreter to indirect through and no compile-time backend env to set -- and backend detection replaced by parsingchimera info'sbuilt:/loaded:lines, which also surfaces the case worth catching: a GPU build whose runtime brought up only CPU. A--binwithout its exec bits ischmod +x'd before use, because a binary downloaded as a GitHub Actions artifact arrives zipped with its POSIX mode stripped. Seedocs/dev/rat.md. -
scripts/case/*.share now cases in that suite. The twelve one-off shell scripts are gone; each survives as arat.pytest target, so they share one model registry, one timeout, one PASS/FAIL summary and one place that knows about--gpu-layers. Thez_turbo*.shscripts becametest-sd-{1..3}-- te-on-cpu + vae-tiling, cpu-offload + vae-on-cpu, and cfg-1 + offload + flash-attn -- mirroring the three cases in cyllama'srwt.pyso the two projects' results compare directly. All three fit an 8 GiB card; the all-on-GPU baseline (~9.4 GiB of weights) and the flash-attn-only variants were dropped, since the baseline OOMs there by construction.run --fastnow runstest-sd-3in place of the oldtest-sd-4. The tworag-chat-qwen3*.shvariants becametest-rag-{1,2}-- which is what found the ingest abort above, since they run at chimera's default chunk window rather than one picked to avoid it.