From 0ee94f21be7f560168b4718d3cc95d8555645e57 Mon Sep 17 00:00:00 2001 From: Mikael Hugo Date: Sat, 2 May 2026 23:25:35 +0200 Subject: [PATCH] chore(sf): drop chatty backfill success log MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit runEmbeddingBackfill fires on every agent_end (per-turn). When the gateway is online and a project produces memories, every turn would write a "[sf:memory-embeddings] WARN: backfill: embedded N memories" line — successes labeled as warnings, repeating on every cycle. That both inflates the stderr stream and misleads grep-for-WARN diagnostics. Successes are routine; the function's return value carries the count when a caller cares. Failures still log (throttled to 60s) via the existing path. Net effect: the embedding pipeline runs silently in the happy path. Co-Authored-By: Claude Opus 4.7 (1M context) --- src/resources/extensions/sf/memory-embeddings.ts | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/resources/extensions/sf/memory-embeddings.ts b/src/resources/extensions/sf/memory-embeddings.ts index ca89f80a1..ee6dc12c3 100644 --- a/src/resources/extensions/sf/memory-embeddings.ts +++ b/src/resources/extensions/sf/memory-embeddings.ts @@ -385,12 +385,9 @@ export async function runEmbeddingBackfill(opts?: { if (count === 0) break; // Stop early to avoid loops on transient saves embedded += count; } - if (embedded > 0) { - logWarning( - "memory-embeddings", - `backfill: embedded ${embedded} memories via ${cfg.embeddingModel}`, - ); - } + // Successes are routine and fire on every agent_end — silent. The + // caller (`runEmbeddingBackfill` consumer) gets the count via the + // return value; failures still log via the throttled path above. return embedded; } finally { backfillInFlight = false;