A feed that was failing stays in the database after its last subscriber leaves #100
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Unsubscribing leaves a feed's row and history behind, which suits a feed that worked. One that never did stays with its error for good, never scanned again: cnn-com (url 'cnn.com', last_error 'relative URL without a base', last checked 2026-09-28 23:26) has no subscription, no catalogue entry, no entries and no files. Found 2026-09-29 checking failing feeds for backoff (#99). Wanted: forget such a feed (no subscribers, not in the catalogue, no file on disk, failing).
Fixed in
0cc956b: the reaper, before each scan, forgets a feed that is failing, has no subscriber, is not in the catalogue and has no file on disk, with its items, file rows, read state and block list. In production it forgot cnn-com on the first scan after the deploy (2026-09-29 19:41). The five other unsubscribed feeds work and were kept.