Files
ipass-plugin-cache/tests/cache/test-cache-capacity.sh
T
ssw 43718bd0c4 iPass cache gateway 源码
容量管理: zones.rs 直读 nginx file_cache 共享内存记账(双轴: 磁盘 + keys_zone 索引内存), ?scan=1 扫盘上限 20 万文件; POST /api/admin/cache/purge 整区清理(只删文件不删目录, 根治 [crit] mkdir failed); POST /api/admin/cache/invalidate 按制品精准失效(预览->确认两步式, glob/子串, 删除上限 5000/扫描上限 20 万); GET /api/admin/cache 新增 capacity 块; 前端容量面板 + 按制品失效工具条; 测试 test-cache-capacity.sh 48/48(容量 27 + 精准失效 21, 含 EXPECT_MIN 护栏与前端静态契约); docs 容量管理章节
2026-09-21 09:25:11 +08:00

536 lines
25 KiB
Bash
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
#!/bin/bash
# ============================================================================
# test-cache-capacity.sh —— 验证「容量管理」这条链路
#
# 回答的问题:缓存占了多大?快不快满?满了谁负责清?能不能现在就腾空间?
#
# 与前两个脚本的分工:
# verify-cache-eviction.sh —— nginx 会不会**自动**淘汰(LRU / inactive)
# 本脚本 —— 网关能不能**看见**容量、能不能**手动**清
#
# 本脚本断言的事(都直连真实实例,走管理 API):
# [1] 容量面板能识别出全部 proxy_cache 区,且**上限来自 conf**(本测把 npm
# 改成 max_size=1m,接口必须如实报 1m —— 证明读数来自 nginx 而非硬编码)
# [2] 空缓存基线:占用 0 / 条目 0 / 水位 0% / 级别 ok
# [3] 写入 3×200KB 后:占用与条目上涨,且**nginx 记账与磁盘实测量级一致**
# [4] `?scan=1` 的磁盘实测 ≈ `du` 实测(±5%)
# [5] 手动清理:删除的是**文件**,`cache/<eco>` 目录必须还在(这是踩过的坑:
# 目录被删后 nginx 不会自愈,此后每次写缓存都 [crit] 并断开客户端)
# [6] 清理后 nginx 记账**滞后**——如实断言它还没归零(把已知行为固化成契约,
# 将来 nginx 行为变了,这条会先亮)
# [7] 清理后同一 URL 再请求:MISS → 200,且 error.log 里没有 crit/mkdir 失败
# [8] 越权与参数校验:账号态(sk_)与未登录都进不来;zone 写错报 400
#
# bash tests/cache/test-cache-capacity.sh
#
# ⚠️ 自起自停一个独立实例(端口 18087 / 假上游 18996),不碰 dev-server;
# 只杀自己记下的 pid,不用 pkill(会误伤别人正在看的实例)。
# ============================================================================
set -uo pipefail
curl() { command curl -s --noproxy '*' "$@"; }
HERE=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
REPO=$(cd "$HERE/../.." && pwd)
RUN="$HERE/.run-cap"
PORT=18087
UP_PORT=18996
NGX="$REPO/build/nginx-1.30.4/objs/nginx"
MOD="$REPO/rust/target/debug/libipass_gateway.dylib"
PY=${PY:-python3}
CACHE_PY="$PY"; export CACHE_PY
# shellcheck source=tests/cache/lib-render.sh
source "$HERE/lib-render.sh"
SK=sk_alice_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
AUTH="Authorization: Bearer $SK"
ADMIN_PW=123456
BODY_SZ=204800 # 每个对象的字节数(200KB)
N=3 # 灌几个对象
pass=0; fail=0
ok() { echo " ✅ $*"; pass=$((pass+1)); }
bad() { echo " ❌ $*"; fail=$((fail+1)); }
cleanup() {
[ -f "$RUN/logs/nginx.pid" ] && kill "$(cat "$RUN/logs/nginx.pid")" 2>/dev/null
[ -f "$RUN/upstream.pid" ] && kill "$(cat "$RUN/upstream.pid")" 2>/dev/null
sleep 0.3
}
trap cleanup EXIT
echo "==== 容量管理验证(独立实例 :${PORT})===="
# ---------- 1. 渲染生产 conf,把 npm 的上限改小到可断言 ----------
cache_write_upstreams "$RUN" "http://127.0.0.1:${UP_PORT}" npm maven || exit 1
cache_render_prod_conf "$RUN" "$PORT" "$MOD" >/dev/null
# ⚠️ 必须拷夹具账号:否则用户表为空 → alice 的 sk_ 不被认 → 全部 401,
# 而 401 在 access 阶段返回、压根不进代理层(症状是「缓存目录 0 文件」)。
cp "$HERE"/fixtures/*.json "$RUN/data/" 2>/dev/null
"$PY" - "$RUN" <<'P'
import re, sys, pathlib
p = pathlib.Path(sys.argv[1], "conf", "nginx.cache.conf")
out = []
for line in p.read_text().splitlines(True):
if "keys_zone=npm:" in line:
line = re.sub(r"max_size=\S+", "max_size=1m", line)
line = re.sub(r"inactive=\S+", "inactive=1h", line)
out.append(line)
p.write_text("".join(out))
print(" [conf] npm: max_size=1m(用于断言「上限读数来自 conf」)")
P
find "$RUN/cache" -type f -delete >/dev/null 2>&1
# ---------- 2. 起假上游(脱离进程组)与 nginx ----------
mkdir -p "$RUN/logs"
: > "$RUN/upstream.log"
UPSTREAM_LOG="$RUN/upstream.log" UPSTREAM_PORT="$UP_PORT" \
"$PY" - "$PY" "$HERE/mock_upstream.py" "$RUN/logs/upstream.out" "$RUN/upstream.pid" <<'P'
import os, subprocess, sys
py, script, out, pidf = sys.argv[1:5]
with open(out, "ab") as f:
p = subprocess.Popen([py, script], stdout=f, stderr=f,
env=dict(os.environ), start_new_session=True)
open(pidf, "w").write(str(p.pid))
P
wait_up() { local p=$1 i=0; until curl -s -o /dev/null --max-time 1 "http://127.0.0.1:$p/$2" 2>/dev/null; do i=$((i+1)); [ $i -ge 80 ] && return 1; sleep 0.1; done; }
wait_up "$UP_PORT" "" || { echo "❌ 假上游未就绪"; exit 1; }
ADMIN_INIT_PASSWORD=x "$NGX" -p "$RUN" -c conf/nginx.cache.conf -t 2>>"$RUN/logs/error.log" \
|| { echo "❌ nginx -t 失败"; tail -10 "$RUN/logs/error.log"; exit 1; }
ADMIN_INIT_PASSWORD=x "$NGX" -p "$RUN" -c conf/nginx.cache.conf
wait_up "$PORT" "" || { echo "❌ nginx 未就绪"; tail -10 "$RUN/logs/error.log"; exit 1; }
echo " 实例就绪(假上游 ${UP_PORT})"
B="http://127.0.0.1:$PORT"
CJ="$RUN/.cookies"
xc() { tr -d '\r' | awk 'tolower($1)=="x-cache-status:"{print $2}'; }
: > "$RUN/logs/error.log.mark"; wc -l < "$RUN/logs/error.log" > "$RUN/logs/error.log.mark"
# 管理会话
curl -c "$CJ" -X POST -H 'Content-Type: application/json' \
-d "{\"username\":\"admin\",\"password\":\"$ADMIN_PW\"}" "$B/api/admin/login" >/dev/null
# 快照 → 写进文件,后续用 jq 式的 python 取值(本机无 jq 也稳)
snap() { # snap [scan] → $RUN/.snap.json
if [ "${1:-}" = "scan" ]; then
curl -b "$CJ" -o "$RUN/.snap.json" "$B/api/admin/cache?scan=1"
else
curl -b "$CJ" -o "$RUN/.snap.json" "$B/api/admin/cache"
fi
}
# 从快照里取一个 zone 的字段:jz <zone> <field>
jz() {
"$PY" - "$RUN/.snap.json" "$1" "$2" <<'P'
import json, sys
d = json.load(open(sys.argv[1]))
cap = d.get("data", d).get("capacity", {})
for z in cap.get("zones", []):
if z.get("zone") == sys.argv[2]:
v = z.get(sys.argv[3])
print("null" if v is None else v)
sys.exit(0)
print("MISSING")
P
}
jtot() { "$PY" -c 'import json,sys; d=json.load(open(sys.argv[1])); print(d["data"]["capacity"]["totals"].get(sys.argv[2],""))' "$RUN/.snap.json" "$1"; }
# ===========================================================================
echo
echo "== 1. 容量区识别与上限来源 =="
snap
"$PY" - "$RUN/.snap.json" <<'P'
import json, sys
d = json.load(open(sys.argv[1]))
cap = d.get("data", d).get("capacity", {})
zones = cap.get("zones", [])
print(" available=%s scanned=%s zones=%d" % (cap.get("available"), cap.get("scanned"), len(zones)))
for z in zones:
print(" %-8s limit=%-10s used=%-8s entries=%-4s idx=%-9s level=%s dir=%s" % (
z["zone"], z["limit_bytes"], z["used_bytes"], z["entries"],
z["keys_zone_bytes"], z["level"], z["dir"]))
P
nzones=$(jtot zones)
if [ "${nzones:-0}" = "6" ]; then
ok "识别出 6 个 proxy_cache 区(go/cargo/pypi/npm/maven/docker)"
else
bad "识别的区数量不是 6(实际 ${nzones:-?})—— 容量读数会缺"
fi
npm_limit=$(jz npm limit_bytes)
if [ "${npm_limit:-0}" = "1048576" ]; then
ok "npm 上限 = 1048576 字节(= conf 里的 max_size=1m)—— 读数确实来自 nginx 配置"
else
bad "npm 上限读数不对(实际 ${npm_limit:-?},期望 1048576)"
fi
npm_dir=$(jz npm dir)
if [ "$npm_dir" = "$RUN/cache/npm" ]; then
ok "npm 的磁盘目录读数正确(${npm_dir})"
else
bad "npm 目录读数不对(实际 ${npm_dir:-?},期望 $RUN/cache/npm)"
fi
npm_routes=$("$PY" - "$RUN/.snap.json" <<'P'
import json, sys
d = json.load(open(sys.argv[1]))
for z in d["data"]["capacity"]["zones"]:
if z["zone"] == "cargo":
print(",".join(z["routes"]))
P
)
if [ "$npm_routes" = "cargo,cargo-dl" ]; then
ok "共享 zone 的路由列全(cargo 区 → cargo,cargo-dl)"
else
bad "cargo 区的路由列表不对(实际 ${npm_routes:-?})"
fi
# ===========================================================================
echo
echo "== 2. 空缓存基线 =="
snap
used0=$(jz npm used_bytes); ent0=$(jz npm entries); pct0=$(jz npm pct); lv0=$(jz npm level)
if [ "${used0:-x}" = "0" ] && [ "${ent0:-x}" = "0" ] && [ "${pct0:-x}" = "0.0" ] && [ "${lv0:-x}" = "ok" ]; then
ok "空缓存:占用 0 / 条目 0 / 水位 0.0% / 级别 ok"
else
bad "空缓存基线不对(used=${used0:-?} entries=${ent0:-?} pct=${pct0:-?} level=${lv0:-?})"
fi
# ===========================================================================
echo
echo "== 3. 写入后(${N} × ${BODY_SZ}B = $((N*BODY_SZ/1024))KB)=="
sample=$(curl -s -o /dev/null -w '%{http_code}' -H "$AUTH" "$B/npm/probe?bytes=1024")
echo " 样本请求 HTTP ${sample}(期望 200;401=Key 不被认,503=上游未配)"
[ "$sample" = "200" ] || { echo "❌ 前置检查失败,后面的容量断言没有意义"; exit 1; }
for i in $(seq 1 $N); do
curl -s -o /dev/null -H "$AUTH" "$B/npm/cap/$i?bytes=$BODY_SZ"
done
sleep 1
snap
used1=$(jz npm used_bytes); ent1=$(jz npm entries); pct1v=$(jz npm pct)
du1=$(du -sk "$RUN/cache/npm" 2>/dev/null | awk '{print $1}')
echo " nginx 记账:${used1} 字节 / ${ent1} 条目 / ${pct1v}% · du 实测:${du1}KB"
if [ "${used1:-0}" -gt 0 ] && [ "${ent1:-0}" -ge "$N" ]; then
ok "占用与条目都涨上来了(${used1}B / ${ent1} 条)"
else
bad "写入后读数没涨(used=${used1:-?} entries=${ent1:-?})"
fi
# 记账 vs 磁盘:两边口径不同,不能要求逐字节相等——
# * nginx 按**块(bsize=4K)向上取整**记账,且只算**文件**;
# * `du` 还包含目录项(levels=1:2 会多出几层目录,每个 4K)。
# 所以判据取一个宽松窗口:「在同一量级」,跨出去才说明两套口径有一个是错的。
du_bytes=$((du1 * 1024))
win=$(( (N + 16) * 4096 ))
lo=$(( du_bytes - win )); [ "$lo" -lt 0 ] && lo=0
hi=$(( du_bytes + win ))
if [ "${used1:-0}" -ge "$lo" ] && [ "${used1:-0}" -le "$hi" ]; then
ok "记账与磁盘同量级(记账 ${used1}B ∈ [${lo}, ${hi}],du=${du_bytes}B)"
else
bad "记账与磁盘量级不符(记账 ${used1}B 不在 [${lo}, ${hi}])"
fi
# ===========================================================================
echo
echo "== 4. 磁盘实测(?scan=1)=="
snap scan
disk1=$(jz npm disk_bytes); dfiles=$(jz npm disk_files)
# 期望文件数 = N + 1:前面那发探针(/npm/probe)也是 200,同样被缓存
EXPECT_FILES=$((N + 1))
echo " disk_bytes=${disk1} disk_files=${dfiles}(期望 ${EXPECT_FILES})du=${du1}KB"
if [ "${dfiles:-0}" -eq "$EXPECT_FILES" ]; then
ok "磁盘实测文件数 = ${dfiles}(探针 1 + 灌入 ${N})"
else
bad "磁盘实测文件数不对(${dfiles:-?},期望 ${EXPECT_FILES})"
fi
lo=$(( du_bytes * 95 / 100 )); hi=$(( du_bytes * 105 / 100 + 4096 ))
if [ "${disk1:-0}" -ge "$lo" ] && [ "${disk1:-0}" -le "$hi" ]; then
ok "磁盘实测 ≈ du(${disk1}B vs ${du_bytes}B,±5%)"
else
bad "磁盘实测与 du 差太多(${disk1:-?} vs ${du_bytes})"
fi
# 总量里也要有磁盘数(证明 totals 汇总没漏)
tdisk=$(jtot disk_bytes)
if [ -n "${tdisk:-}" ] && [ "$tdisk" != "None" ]; then
ok "totals 里带了磁盘实测汇总(${tdisk}B)"
else
bad "totals 缺磁盘实测汇总"
fi
# ===========================================================================
echo
echo "== 5. 越权与参数校验 =="
c1=$(curl -s -o /dev/null -w '%{http_code}' -X POST -H 'Content-Type: application/json' \
-d '{"zone":"npm"}' "$B/api/admin/cache/purge")
c2=$(curl -s -o /dev/null -w '%{http_code}' -X POST -H "Authorization: Bearer $SK" \
-H 'Content-Type: application/json' -d '{"zone":"npm"}' "$B/api/admin/cache/purge")
[ "$c1" = "401" ] && ok "未登录调 purge → 401" || bad "未登录调 purge 得到 ${c1}(期望 401)"
[ "$c2" = "401" ] && ok "账号态 sk_ 调 purge → 401(管理动作不给普通 Key)" \
|| bad "账号态调 purge 得到 ${c2}(期望 401)—— 这是个安全口子"
r=$(curl -s -b "$CJ" -X POST -H 'Content-Type: application/json' -d '{"zone":"nope"}' \
"$B/api/admin/cache/purge")
echo " zone=nope → $r"
case "$r" in
*未知*|*unknown*|*已知*) ok "未知 zone 被拒(400 且说清了已知值)" ;;
*) bad "未知 zone 没被拒:$r" ;;
esac
r=$(curl -s -b "$CJ" -X POST -H 'Content-Type: application/json' -d '{}' "$B/api/admin/cache/purge")
case "$r" in
*缺少*) ok "缺 zone 参数被拒" ;;
*) bad "缺 zone 参数没被拒:$r" ;;
esac
# ===========================================================================
echo
echo "== 6. 手动清空 npm 区(只删文件,目录必须留下)=="
r=$(curl -s -b "$CJ" -X POST -H 'Content-Type: application/json' -d '{"zone":"npm"}' \
"$B/api/admin/cache/purge")
echo " $r"
fdel=$("$PY" -c 'import json,sys; print(json.loads(sys.argv[1])["data"]["total"]["files"])' "$r" 2>/dev/null)
bdel=$("$PY" -c 'import json,sys; print(json.loads(sys.argv[1])["data"]["total"]["bytes"])' "$r" 2>/dev/null)
left=$(find "$RUN/cache/npm" -type f 2>/dev/null | wc -l | tr -d ' ')
[ "${fdel:-0}" -ge "$N" ] && ok "接口报告删除了 ${fdel} 个文件 / ${bdel} 字节" \
|| bad "接口报告的删除数不对(${fdel:-?})"
[ "${left:-9}" = "0" ] && ok "磁盘上文件已清零" || bad "磁盘还有 ${left} 个文件没删掉"
if [ -d "$RUN/cache/npm" ]; then
ok "★ cache/npm 目录仍在(删目录会让该路由 [crit] 直到 restart,这里必须保留)"
else
bad "★★ cache/npm 目录被删了 —— 这条路由接下来每次写缓存都会失败"
fi
snap scan
disk2=$(jz npm disk_bytes)
oneeds=$(jz npm entries)
[ "${disk2:-x}" = "0" ] && ok "磁盘实测归零(disk_bytes=0)" || bad "磁盘实测没归零(${disk2:-?})"
# ★ 已知行为:nginx 的记账**不会**因文件被外部删除而立刻回落。
# 节点要等「该 key 再被访问(发现文件不在)」或「条目到期」才回收。
# 这里把它固化成契约:如果哪天 nginx 改了这行为,这条会先亮,提示我们更新文档。
if [ "${oneeds:-0}" -gt 0 ]; then
ok "nginx 记账仍滞后(entries=${oneeds},磁盘已 0)—— 与文档一致:面板不会假装账已平"
else
echo " ⚠️ nginx 记账已同步归零(entries=0):行为与预期不同,请更新 docs/§容量与淘汰"
fi
# 清空后**再访问**:必须 MISS→200(正确性:不会返回脏数据、不会 500)
echo " -- 清空后重新拉一次(应 MISS 回源重建)--"
st=$(curl -s -D - -o /dev/null -H "$AUTH" "$B/npm/cap/1?bytes=$BODY_SZ" | xc)
code=$(curl -s -o /dev/null -w '%{http_code}' -H "$AUTH" "$B/npm/cap/1?bytes=$BODY_SZ")
[ "$st" = "MISS" ] && ok "清空后再请求 = MISS(不会返回脏数据)" || bad "清空后再请求是 ${st}(期望 MISS)"
[ "$code" = "200" ] && ok "清空后再请求 200(缓存重建正常)" || bad "清空后再请求 HTTP ${code}"
# 关键:清理动作绝不能把目录搞坏 —— 检查 nginx 有没有报 crit / mkdir 失败
ncrit=$(tail -n +"$(cat "$RUN/logs/error.log.mark")" "$RUN/logs/error.log" 2>/dev/null | grep -c "crit\|mkdir() failed")
if [ "${ncrit:-1}" = "0" ]; then
ok "error.log 无 crit / mkdir 失败(目录结构完好)"
else
bad "error.log 出现 ${ncrit} 条 crit/mkdir 失败 —— 目录被破坏了"
tail -5 "$RUN/logs/error.log"
fi
# ===========================================================================
echo
echo "== 7. zone=all 全清 =="
r=$(curl -s -b "$CJ" -X POST -H 'Content-Type: application/json' -d '{"zone":"all"}' \
"$B/api/admin/cache/purge")
fdel=$("$PY" -c 'import json,sys; print(json.loads(sys.argv[1])["data"]["total"]["files"])' "$r" 2>/dev/null)
leftall=$(find "$RUN/cache" -type f 2>/dev/null | wc -l | tr -d ' ')
dirs=$(ls "$RUN/cache" | tr '\n' ' ')
[ "${leftall:-9}" = "0" ] && ok "全部区已清空(含 maven 等)" || bad "仍有 ${leftall} 个文件"
[ "$dirs" = "cargo docker go maven npm pypi " ] \
&& ok "六个缓存目录都还在(${dirs})" \
|| bad "目录结构异常:$dirs"
echo " (all 删除 ${fdel} 个文件)"
echo
# ===========================================================================
# 按制品失效(purge 的细一档粒度)
# 「上游把某个版本发坏了」时真正要扔的只有几个文件,清掉整个生态 = 几十 GB 白重拉。
# ===========================================================================
echo "== 8. 按制品失效(先预览、再确认;只删文件不删目录)=="
IV="$B/api/admin/cache/invalidate"
nfiles() { find "$RUN/cache" -type f 2>/dev/null | wc -l | tr -d ' '; }
# inv <body> [curl 额外参数...] → 打 HTTP 码到 stdout,响应落到 $RUN/.inv.json
inv() {
local body=$1; shift
curl -s -o "$RUN/.inv.json" -w '%{http_code}' -X POST -H 'Content-Type: application/json' \
-d "$body" "$@" "$IV"
}
iv() { "$PY" -c 'import json,sys; d=json.load(open(sys.argv[1])); print(d["data"]["total"][sys.argv[2]])' "$RUN/.inv.json" "$1"; }
# 造四个可区分的条目:两个 npm、一个 maven,外加一个「不该被误伤」的对照
curl -s -o /dev/null -H "$AUTH" "$B/npm/keep-a/1?bytes=$BODY_SZ"
curl -s -o /dev/null -H "$AUTH" "$B/npm/dropme/1?bytes=$BODY_SZ"
curl -s -o /dev/null -H "$AUTH" "$B/maven/keep-m/1?bytes=$BODY_SZ"
sleep 0.3
n0=$(nfiles)
echo " (起始 ${n0} 个缓存文件)"
# --- 8.1 预览:必须只算不删 ---
code=$(inv '{"match":"dropme"}' -b "$CJ")
[ "$code" = "200" ] && ok "预览返回 200" || bad "预览返回 ${code}"
[ "$(iv matched)" = "1" ] && ok "预览命中 1 个(dropme)" || bad "预览命中数不对($(iv matched))"
[ "$(iv deleted)" = "0" ] && ok "★ 预览 deleted=0(未传 apply 时绝不删)" || bad "预览竟然删了 $(iv deleted) 个"
[ "$(nfiles)" = "$n0" ] && ok "★ 预览后磁盘文件数不变(${n0})" || bad "预览动了盘:$n0 → $(nfiles)"
# 命中的 key 要回显出来 —— 否则用户没法确认表达式对不对
if "$PY" - "$RUN/.inv.json" <<'P'
import json, sys
d = json.load(open(sys.argv[1]))["data"]
if "keys" not in json.dumps(d):
print(" ❌ 响应里没有 keys 字段(用户看不到命中什么,等于没法确认表达式)")
sys.exit(1)
keys = [k for it in d["items"] for k in it["keys"]]
good = any("dropme" in k for k in keys)
print((" ✅ " if good else " ❌ ") + "预览回显命中的 cache key:" + (keys[0] if keys else "(空)"))
sys.exit(0 if good else 1)
P
then pass=$((pass+1)); else fail=$((fail+1)); fi
# --- 8.2 真删:只删命中项,对照项必须留下 ---
code=$(inv '{"match":"dropme","apply":1}' -b "$CJ")
[ "$code" = "200" ] && ok "失效返回 200" || bad "失效返回 ${code}"
[ "$(iv deleted)" = "1" ] && ok "应用后删除 1 个" || bad "删除数不对($(iv deleted))"
[ "$(nfiles)" = "$((n0-1))" ] && ok "磁盘文件数 $n0 → $((n0-1))(只少了命中的那个)" \
|| bad "文件数异常:$n0 → $(nfiles)"
if [ -d "$RUN/cache/npm" ]; then
ok "★ cache/npm 目录仍在(与 purge 同一条硬约束)"
else
bad "★★ cache/npm 目录被删了 —— 该路由接下来会持续 [crit]"
fi
# 对照项没被误伤:keep-a 仍在盘上(按 key 找)
if "$PY" - "$RUN/cache" <<'P'
import glob, os, sys
root = sys.argv[1]
found = []
for p in glob.glob(os.path.join(root, "**", "*"), recursive=True):
if os.path.isfile(p):
with open(p, "rb") as f:
h = f.read(4096)
i = h.find(b"KEY: ")
if i >= 0:
found.append(h[i + 5:h.find(b"\n", i)].decode("utf-8", "replace"))
hit = [k for k in found if "keep-a" in k]
print((" ✅ " if hit else " ❌ ") + "对照项 keep-a 未被误伤(现存 " + str(len(found)) + " 个 key)")
sys.exit(0 if hit else 1)
P
then pass=$((pass+1)); else fail=$((fail+1)); fi
# --- 8.3 删后重新拉:MISS → 200,缓存重建(正确性不受影响)---
st=$(curl -s -D - -o /dev/null -H "$AUTH" "$B/npm/dropme/1?bytes=$BODY_SZ" | xc)
code=$(curl -s -o /dev/null -w '%{http_code}' -H "$AUTH" "$B/npm/dropme/1?bytes=$BODY_SZ")
[ "$st" = "MISS" ] && ok "失效后再请求 = MISS(不会返回脏数据)" || bad "失效后再请求是 ${st}(期望 MISS)"
[ "$code" = "200" ] && ok "失效后再请求 200(缓存重建正常)" || bad "失效后再请求 HTTP ${code}"
# --- 8.4 glob 匹配 ---
code=$(inv '{"match":"npm:/npm/keep*"}' -b "$CJ")
[ "$code" = "200" ] && [ "$(iv matched)" = "1" ] \
&& ok "glob 'npm:/npm/keep*' 命中 1 个" || bad "glob 匹配异常(matched=$(iv matched))"
code=$(inv '{"match":"*keep*"}' -b "$CJ")
[ "$(iv matched)" = "2" ] && ok "glob '*keep*' 跨生态命中 2 个(npm keep-a + maven keep-m)" \
|| bad "跨生态 glob 命中数不对($(iv matched))"
# --- 8.5 zone 限定:只在指定区里搜 ---
code=$(inv '{"zone":"npm","match":"keep-m"}' -b "$CJ")
[ "$(iv matched)" = "0" ] && ok "zone=npm + match=keep-m → 0(不会跨区误伤)" \
|| bad "zone 限定失效($(iv matched))"
# --- 8.6 无命中:200 且不报错(最常见的原因是关键字写错)---
code=$(inv '{"match":"nosuchartifact"}' -b "$CJ")
[ "$code" = "200" ] && [ "$(iv matched)" = "0" ] \
&& ok "无命中时返回 200 / matched=0(不当作错误)" || bad "无命中返回 ${code}/$(iv matched)"
# --- 8.7 参数与越权 ---
code=$(inv '{}' -b "$CJ")
[ "$code" = "400" ] && ok "缺 match → 400" || bad "缺 match 返回 ${code}"
code=$(inv '{"zone":"nope","match":"x"}' -b "$CJ")
[ "$code" = "400" ] && ok "未知 zone → 400" || bad "未知 zone 返回 ${code}"
code=$(inv '{"match":"x"}')
[ "$code" = "401" ] && ok "未登录 → 401" || bad "未登录返回 ${code}"
code=$(inv '{"match":"x","apply":1}' -H "$AUTH")
[ "$code" = "401" ] && ok "账号态 sk_ 调失效 → 401(破坏性动作不给普通 Key)" || bad "sk_ 返回 ${code}"
# --- 8.8 清理动作不能把目录搞坏 ---
ncrit=$(tail -n +"$(cat "$RUN/logs/error.log.mark")" "$RUN/logs/error.log" 2>/dev/null | grep -c "crit\|mkdir() failed")
if [ "${ncrit:-1}" = "0" ]; then
ok "error.log 无 crit / mkdir 失败(目录结构完好)"
else
bad "error.log 出现 ${ncrit} 条 crit/mkdir 失败"
tail -5 "$RUN/logs/error.log"
fi
echo
# ===========================================================================
# 前端静态契约:API 全绿 ≠ 面板看得见。
# 曾经踩过:renderCapacity() 写好了、锚点也都在,但 render() 里漏了那一行调用
# → 接口返回 100% 正确、后端断言全绿,而面板是**空的**。
# 这条断言专治「定义了却没人调用」。
echo "== 9. 前端静态契约(面板锚点齐 + 渲染函数真的被调用)=="
out=$("$PY" - "$REPO/www/cache.html" "$REPO/www/assets/cache.js" <<'PYCODE'
import re, sys
html = open(sys.argv[1], encoding="utf-8").read()
js = open(sys.argv[2], encoding="utf-8").read()
ok_, bad_ = [], []
need = ["capBody", "capSummary", "capRefresh", "capScan", "capPurgeAll",
"capMatch", "capZone", "capPreview", "capApply",
"capInvalResult", "capInvalKeys"]
missing = [a for a in need if ('id="%s"' % a) not in html]
if missing:
bad_.append("cache.html 缺锚点:" + " ".join(missing))
else:
ok_.append("cache.html 含全部容量面板锚点(%d 个)" % len(need))
# 每个 `function NAME(` 定义,名字在全文至少要出现 2 次(定义 + 至少一处调用/引用)
defs = re.findall(r"\bfunction\s+([A-Za-z_$][\w$]*)\s*\(", js)
dead = sorted({n for n in defs if len(re.findall(r"\b%s\b" % re.escape(n), js)) < 2})
if dead:
bad_.append("定义了但从未被引用的函数:" + " ".join(dead))
else:
ok_.append("cache.js 无「定义了却没人调用」的函数(共 %d 个定义)" % len(defs))
# 容量渲染必须由 render() 以语句形式调用(只被别处引用不算「面板会渲染」)
for n in ["renderCapacity"]:
if not re.search(r"^\s*%s\(\);" % re.escape(n), js, re.M):
bad_.append("%s() 没有任何一处以语句形式调用(render() 里漏了?)" % n)
else:
ok_.append("%s() 已在 render() 的语句位置被调用" % n)
for s in ok_:
print("OK " + s)
for s in bad_:
print("BAD " + s)
if len(ok_) + len(bad_) < 3:
# 走到这里说明这段断言自己没跑完(如被编辑弄出语法错)——
# 必须显式失败:否则「断言静默消失」会伪装成全绿(踩过:3 条变成 0 条,fail 仍是 0)
print("BAD 静态契约断言未完整执行(只产出 %d 条)" % (len(ok_) + len(bad_)))
PYCODE
)
pyrc=$?
while IFS= read -r line; do
case "$line" in
OK\ *) echo " ✅ ${line#OK }"; pass=$((pass+1)) ;;
BAD\ *) echo " ❌ ${line#BAD }"; fail=$((fail+1)) ;;
esac
done <<< "$out"
if [ "$pyrc" -ne 0 ]; then
echo " ❌ 静态契约检查脚本自身出错(python 退出码 $pyrc)—— 上面没有 ✅ 不代表通过"
fail=$((fail+1))
fi
echo
# 防「断言静默消失」:本脚本的断言条数**本身是契约**。曾经因为一次编辑把 python
# 块的换行吞掉,3 条前端断言直接没跑,而 fail=0、结果看着是全绿。
# 所以这里钉一个下限:新增/删除断言时同步改这个数(改它比漏掉断言安全)。
EXPECT_MIN=48
if [ "${pass}" -lt "$EXPECT_MIN" ]; then
echo " ❌ 通过数 ${pass} < 预期下限 ${EXPECT_MIN}:有断言没跑到(被改坏或被静默跳过)"
fail=$((fail+1))
fi
echo "==== 结果:通过 ${pass},失败 ${fail}(期望下限 ${EXPECT_MIN})===="
echo "要删净临时目录: rm -rf $RUN"
[ "$fail" -eq 0 ] || exit 1