fix(news): keep a refused key refused during a slow read, and read Local when Conflicts fails

A slow re-read of a refused key read as unavailable until it landed; it
now stays refused. The first-read wait is 10 s, for a margin under the
browser's 15 s. A failed Conflicts read no longer stops Local's refresh,
which the server reads on its own. Tests cover GDELT's wait, the refused
key and a caller abort past the timeout, and fail rather than hang; the
docs say what a section serves meanwhile.
This commit is contained in:
Denis Groshev committed 2026-11-06 12:02:58 +01:00
1 parent c6ae4c44d7
commit 61424e4256
7 files changed
+176 -42

No files matched your search

+2
View File
@@ -1428,6 +1428,8 @@ export function createNewsLayer({
}
unavailable = cause?.unavailable === true;
error = cause?.message || FEED_UNAVAILABLE;
// Local is read apart: Conflicts failing leaves it reading.
void refreshInView({ force: inView.active });
return true;
} finally {
signal?.removeEventListener('abort', abort);