From 3ee14819b7bd905c935ff34270e951097ded5d9d Mon Sep 17 00:00:00 2001 From: Ethanfel Date: Fri, 3 Jul 2026 11:07:58 +0200 Subject: [PATCH] diag: text gate build marker in console (confirm loaded JS) Loading a workflow does not re-fetch extension JS, and aiohttp serves web/*.js with only Last-Modified (no no-store), so an open tab can keep running a cached old text_gate.js. Log a build tag on setup so we can tell from the devtools console whether the persistence/weighting build is actually loaded. Co-Authored-By: Claude Opus 4.8 --- web/text_gate.js | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/web/text_gate.js b/web/text_gate.js index a975a05..993d02c 100644 --- a/web/text_gate.js +++ b/web/text_gate.js @@ -255,11 +255,18 @@ function setupTextGateNode(node) { syncWidgetWidth(node); } +// Build marker — lets you confirm the browser loaded THIS build (not a cached +// old copy). If the editor comes back empty after reload but you don't see this +// line in the devtools console, your tab is running stale JS: hard-refresh +// (Ctrl/Cmd+Shift+R). +const BUILD = "2026-07-03 persist+weight"; + app.registerExtension({ name: "datasete.gates.textgate", // one global socket listener: route the server's pause event to the node setup() { + console.info(`[datasete.textgate] loaded build ${BUILD}`); api.addEventListener("datasete-textgate-show", (e) => { const d = e.detail || {}; const node = app.graph?.getNodeById?.(parseInt(d.id, 10));