From efa861f227315dc81f6b464ac95bcf5ef3f42f6c Mon Sep 17 00:00:00 2001
From: gator
Date: Thu, 17 Sep 2026 12:51:27 +0000
Subject: [PATCH] Recover from a job killed by a deploy, and show when a cut
reorders
cuts_state is set before the thread starts and cleared when it finishes, so
a deploy in between left the page waiting forever on work that was no longer
running, with the retry button hidden. Fifteen minutes is longer than the
work can legitimately take.
A cut may reorder as well as drop, which changes what it is - worth saying
rather than leaving the reader to spot it in the id list.
---
trailer.html | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/trailer.html b/trailer.html
index 556e0ef..832b8af 100644
--- a/trailer.html
+++ b/trailer.html
@@ -332,7 +332,7 @@
+ 'Each other model reads ONLY this script - no book - and says what it understood.">'
+ (REVIEWS.length ? "Test it again" : "Does it make sense? Ask " + others + " readers")
+ '');
- if ((PKG.shots || []).length >= 6 && String(PKG.cuts_state || "") !== "thinking")
+ if ((PKG.shots || []).length >= 6 && !busyCuts())
out.push('
';
- if (st === "thinking") out += '
Working out what to drop…
';
+ if (busyCuts()) out += '
Working out what to drop…
';
+ else if (st === "thinking") out += '
The last attempt stopped '
+ + 'before it finished — the server restarted under it. Ask again.