asepharyanaandClaude Opus 5
d2e97ae11d
- gateway-metrics: collectors now run per scrape so Prometheus sees real data (process memory/uptime + live AI-analysis pipeline gauges) instead of an always-empty stub. bootstrap registers the pipeline collectors. - systemd: MemoryMax 512M -> 1G (live RSS ~500MiB, peak 508MiB; 512M left ~2% headroom and risked an OOM-kill restart; host has 8GB free). - config: POSTGRES_POOL_MIN 2 -> 0 so main + 4 Piscina worker threads don't hold ~10 permanently-open idle pg connections against PgBouncer. - docs: rewrite stale ARCHITECTURE.md / MODULE_STRUCTURE.md (winston -> pino, removed mock-crc/indonesianTextNormalizer, renamed aiAnalysisWorker/llmModerationClient). Verified: tsc clean, 129 vitest pass, biome clean on changed files. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
52 lines
2.6 KiB
TypeScript
52 lines
2.6 KiB
TypeScript
// ═══════════════════════════════════════════════════════════════════════════
|
|
// makeImageCacheKey — regression for hash collision bug
|
|
// ═══════════════════════════════════════════════════════════════════════════
|
|
// Bug (2026-08-12): makeImageCacheKey() only hashed the first 128 chars of the
|
|
// data URL. Since all resized images share the same MIME prefix
|
|
// ('data:image/png;base64,') + identical base64 header bytes, nearly every
|
|
// image got the SAME hash → 'image:<same-hash>' → all images reused the
|
|
// first cached vision analysis ("konten judi").
|
|
//
|
|
// Fix: hash the ENTIRE data URL. This test verifies the fix and prevents
|
|
// regression.
|
|
import { createHash } from "node:crypto";
|
|
import { describe, expect, it } from "vitest";
|
|
import { makeImageCacheKey } from "../src/modules/ai-moderation/textCacheStore.js";
|
|
|
|
function oldBuggyHash(dataUrl: string): string {
|
|
const prefix = dataUrl.slice(0, 128);
|
|
return `image:${createHash("sha256").update(prefix).digest("hex").slice(0, 16)}`;
|
|
}
|
|
|
|
describe("makeImageCacheKey — collision prevention", () => {
|
|
it("produces different keys for images whose first 128 chars are identical", () => {
|
|
// Two data URLs that SHARE the first 128 chars (same MIME + identical
|
|
// base64 header) but differ after — this is the real-world scenario
|
|
// that caused the collision bug.
|
|
const sharedPrefix =
|
|
"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNk+M9QDwADhgGAWjR9awAAAABJRU5ErkJggg==" +
|
|
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"; // pad to >128 chars
|
|
|
|
const imgA = `${sharedPrefix}UNIQUE_TO_A`;
|
|
const imgB = `${sharedPrefix}UNIQUE_TO_B`;
|
|
|
|
// Under the OLD buggy scheme: same prefix → same hash → COLLISION
|
|
expect(oldBuggyHash(imgA)).toBe(oldBuggyHash(imgB));
|
|
|
|
// Under the FIXED scheme: full data URL hashed → different keys
|
|
const keyA = makeImageCacheKey(imgA);
|
|
const keyB = makeImageCacheKey(imgB);
|
|
expect(keyA).not.toBe(keyB);
|
|
});
|
|
|
|
it("produces same key for identical input", () => {
|
|
const dataUrl = "data:image/png;base64,samebase64dataheremari";
|
|
expect(makeImageCacheKey(dataUrl)).toBe(makeImageCacheKey(dataUrl));
|
|
});
|
|
|
|
it("prefix is always 'image:'", () => {
|
|
const key = makeImageCacheKey("data:image/png;base64,test");
|
|
expect(key.startsWith("image:")).toBe(true);
|
|
});
|
|
});
|