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.

ci(fuzz): seed the fuzz workspace's lockfile from engine/Cargo.lock

xerj-org3747a373fa4d
diff --git a/.github/scripts/fuzz-smoke.sh b/.github/scripts/fuzz-smoke.sh
index ba6ed9f1c..186c1de0e 100755
--- a/.github/scripts/fuzz-smoke.sh
+++ b/.github/scripts/fuzz-smoke.sh
@@ -49,6 +49,19 @@ fi
cd "$REPO_ROOT/engine"
+# The fuzz crate is its own workspace with no committed lockfile, so every
+# run used to resolve its dependency graph fresh from crates.io. When upstream
+# yanked every `zip 8.x` release (2026-10-16), that fresh resolve failed with
+# "failed to select a version for the requirement `zip = "^8"`" on every
+# branch, while the engine itself still built from its locked `zip 8.6.0`.
+# Start the fuzz workspace from the engine's lockfile instead: the fuzz build
+# then uses exactly the versions the engine ships and tests (a locked yanked
+# version stays usable), and cargo only adds the fuzz-only crates on top.
+# A contributor's own fuzz/Cargo.lock is left alone.
+if [ ! -f fuzz/Cargo.lock ]; then
+ cp Cargo.lock fuzz/Cargo.lock
+fi
+
echo "==> building fuzz targets (ASan + libFuzzer)"
cargo +nightly fuzz build