From fce4e1a5838d959a406f1d2979fcb560ae61efa7 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Sun, 4 Oct 2026 11:16:24 -0700 Subject: [PATCH] chore(albok-service): 0.1.8 on nh3-docker (e653c29; fleet/memory reindex on new tag) --- stacks/albok-service/README.md | 11 ++++++----- stacks/albok-service/compose.yaml | 2 +- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/stacks/albok-service/README.md b/stacks/albok-service/README.md index df4bdda..d13ed2b 100644 --- a/stacks/albok-service/README.md +++ b/stacks/albok-service/README.md @@ -6,11 +6,12 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`, - **URL:** `http://albok.nh3.internal:8392` (= `http://10.100.50.40:8392`). Container port 8390. ⚠ Host port **8392**, because **8390 on nh3-docker is the althing post office**. -- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.7` @ `sha256:0dbb8cc7…` (pinned in `compose.yaml`), built - 2026-10-04 ~0755 from vh/albok `64f75dc` (tag albok-service/v0.1.7; pushed by infra-hermes on albok-dev's hand-down via infra-ops). - Deployed between Nemi walks; fleet/stash + personal/agent-feedback reindexed on it. fleet/memory reindex was - stood down (HOLD, msg 01M43QWC7HBTYSH8G1NSTJA4F7): the heid re-pass found real drift in 0.1.7 and 0.1.8 follows — - on the new tag, all three reindexes run in the original order. +- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.8` @ `sha256:239f900e…` (pinned in `compose.yaml`), built + 2026-10-04 ~1115 from vh/albok `e653c29` (tag albok-service/v0.1.8; heid re-pass fixes over 0.1.7: keyword-index + lock mismatch, journal-stranding replay path, bypassable 400, link-kind handling in the collapse). fleet/memory + reindexed on it per albok-dev (their 0.1.7 stash + agent-feedback reindexes stand — 0.1.8 does not change what a + reindex writes). + Prior: 0.1.7 `sha256:0dbb8cc7…` (64f75dc), fleet/stash + personal/agent-feedback reindexed on it. Prior: 0.1.6 `sha256:2b44c9d4…`, built 2026-10-04 ~0544 from vh/albok `6c1adcd` (tags albok-service/v0.1.6 + core v0.1.4; pushed by infra-ops on Prime's go). 0.1.6 is the review fold on 0.1.5's search fix: the keyword-index build now takes a lock (two concurrent first queries could cross diff --git a/stacks/albok-service/compose.yaml b/stacks/albok-service/compose.yaml index f34cb44..a759704 100644 --- a/stacks/albok-service/compose.yaml +++ b/stacks/albok-service/compose.yaml @@ -12,7 +12,7 @@ # 1512 albok-feedback (restricted wing personal/agent-feedback) is default-deny: no viewer gets it. services: albok-service: - image: gitea.phasefinal.com/pfi/albok-service:0.1.7@sha256:0dbb8cc7fc86808feab1d352d6cd701deed28d1e82b67e4c1d9331e6b62d4540 + image: gitea.phasefinal.com/pfi/albok-service:0.1.8@sha256:239f900ee39a26414f34afe9b7583253986d838df9988228fab1039d18c414df container_name: albok-service restart: unless-stopped ports: