You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
spark do --sandbox runs on bubblewrap 0.8 to 0.10, Debian 12's and
Ubuntu 24.04's, where --overlay does not exist yet. There the
project is copied into the run and bound over itself (the copy mode, sandbox.linux_mode), and the review and the apply read the copy
against the project as macOS's clone is read. The probe's refusal
under Ubuntu's AppArmor userns switch names the switch and the way
round it. CI proves it in debian:12 and ubuntu:24.04 containers, tests/gate.sh full sandbox and the sandbox row (#155).
A trust by hand is pinned. spark mcp trust NAME on writes MCP_SERVER_<NAME>_PIN, the program's sha256 and each tool's flag as
listed then. A program that changed, or an older trust with no pin,
reads as not trusted and the mcp row says so with the remedy. A
tool whose flags ask less than the pin's did, or one the pin never
saw, takes the typed yes again until the person trusts the server
again (#154).
spark setup finds a llama-server of yours on llama-server's own
default port, 9931 since b11960, as well as on SPARK_PORT
(setup.ENGINE_PORTS), and offers the one that answers. SPARK_PORT
stays 8080 (#153).
The engine pin moves from llama.cpp b10689 to b11960 (2026-10-28,
0.8.0): the six tarballs fetched, their sha256 taken and their build
attestations verified against ggml-org/llama.cpp. Every flag spark
passes is in the new server's own table, and the glibc floor is the
old one, 2.34 on x86_64 and 2.38 on aarch64. llama-server's own
default port is 9931 there; spark's stays 8080 (#152).
The engine starts with a clean environment: engine.ENV_KEEP and engine.ENV_PREFIXES name what it gets (its path, its locale, the
GPU variables), and every LLAMA_ARG_* of a shell is dropped, so
none can point it at another host. Its command carries --offline.
The serve row warns on a connection the engine holds to another
host (engine.outbound) (#151).
voice.env says why the runtime is held at sherpa-onnx 1.13.8: 2.0.0
builds espeak-ng out and ignores the data_dir Kokoro reads
espeak-ng-data through, so the pt-BR voice would go silent. It moves
only with phonemes made on this side, for English and pt-BR both. tests/voice_test.py fails a bump before that (#150).