Skip to content

armgit / xerj

Public Imported from GitHub
0

AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.

Merge remote-tracking branch 'origin/main' into fix/silent-retry-envelope

xerj-org37b1b0d8af59
diff --cc CHANGELOG.md
index 8c160eb5a,60dfe3510..3d87299dd
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -9,20 -9,25 +9,39 @@@ and this project adheres to [Semantic V
### Fixed
+ - **`xerj corpus index` now proves the store answers a search before it says "searchable"** (issue
+ [#1183](https://github.com/xerj-org/xerj/issues/1183)) — a resume over an index left with a
+ dangling segment by a killed finalize printed `corpus 'xerj-search' searchable: 642 records`
+ and exited 0 while the store answered every `_search` — and the salvage path's own
+ `delete_by_query` — with `store_exception: Segment … not found`. `_count` is metadata-only and
+ returned 642 over that same store, so every verification built on counts certified a corpus
+ that could not be queried. Verification now has a third leg: one `size:0` `_search` over
+ exactly the glob `xerj code` reads (`{prefix}-*`), with the node's own reason surfaced when it
+ fails. In the build arm a build whose verification search fails is not verified — nothing is
+ switched, the existing index stays what `xerj code` serves, and the unsearchable build's own
+ indices are retired by exact name (an unsearchable index left under the namespace is what
+ poisoned the live one); the #367 salvage can no longer record a store that cannot be searched.
+ The update arm refuses to rewrite the ledger over a live corpus that cannot be searched, and
+ the legacy arm — the exact live failure — refuses to print any verdict at all, because one
+ unsearchable index anywhere under the wildcard makes "the corpus is queryable" untrue whatever
+ the counts said. The probe is a `size:0` search, which the server already classifies as
+ machine traffic in the audit log (#1109), so `xerj gain` still measures only the user's
+ queries. The finalize-catalog deadlock that produces the dangling segment (item 1 of #1183)
+ remains open, tracked in the same issue.
+- **A request retrying after a transport error or a 5xx now says so on stderr** (part of issue
+ [#1183](https://github.com/xerj-org/xerj/issues/1183)) — the autoindex client's retry envelope
+ is bounded (six attempts at a 300 s request timeout each, ≈31 min worst case) but was
+ completely silent on everything except HTTP 429, which is how the #1183 incident read as a
+ deadlock: a finalize-catalog request against a memory-pressured node spent eight minutes inside
+ that envelope with zero output, and since `reqwest::blocking` parks the caller on a oneshot,
+ every thread's `/proc` wchan read `futex_do_wait` — indistinguishable from a lock cycle at that
+ granularity. Diagnosis in the issue: it was never a deadlock; the silence was the defect. A
+ loading run (announce on) now prints `autoindex: search failed: …; retrying (attempt 2 of 6,
+ … s in this request so far)` on the first failure and at most once per 30 s after, sharing the
+ 429 notice's clock so alternating failures cannot double-announce; probes, MCP clients and
+ `--quiet` stay silent. The server-side stall root cause (the reference node running at its
+ memory breaker during large rebuilds) remains open under #1183 and the #1122 memory-ceiling
+ class.
## [1.0.0-rc.86] - 2026-10-06