1.3 KiB
albok-service 0.1.2 LIVE on nh3-docker (albok-dev ask 6955, 0251), fixing a leak that had broken 0.1.1
[2026-10-03] albok-service 0.1.2 LIVE on nh3-docker (albok-dev ask 6955, 0251), fixing a leak that had broken 0.1.1. 0.1.1 leaked a Chroma client per health probe: after 9 h it held 1018 of 1024 fds and /health//search answered 500. 0.1.2 (sha256:6f91a33f…, built from albok-dev's LOCAL 544ecfd before the push; origin's tags verified = 544ecfd at 1000) holds 59 fds, 0 deleted, over 30 health calls. Added restricted wing personal/agent-feedback (group albok-feedback 1512, default-deny). Nemi credentials: service token re-minted with agent-feedback grants (albok/token-nemi; old token still live until albok-dev revokes it) and LiteLLM key albok-nemi (gen-small/summarizer/qwen3-embedding; albok/litellm-key-nemi). Nemi timer INSTALLED 0559 (user units albok-nemi.{service,timer} on nh3-dev, hourly; OnFailure → infra-ops inbox; services/albok-nemi/). Gate: albok-dev's steady-state walk, median 594 s over n=3; my test walk through the unit took 589 s with exit 0. ⚠ Reports grow ~55 MB/day (retention asked of albok-dev); manual walks go through systemctl --user start albok-nemi.service (no overlap). → stacks/albok-service/README.md