Retire davewiner's 922 rows, without taking the 12 that people still read #3
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?
The OPML left
config.tomlbeforeretire_group(src/main.rs:966) existed, so nothing retired its derived feeds; the backstop insubscriptions()(src/main.rs:927) skips them forever instead. Their stalelast_errortext accounts for 55 of the 76 stored errors.910 of them nobody subscribes to: 791 have no files and should be dropped, 119 have files and should be marked orphaned.
The other 12 (xkcd, The Verge, TechCrunch, Hacker News and others, held by users 2 and 3) were promoted into
config.tomland are scanned from there, but their rows still saymanaged = 1.managed_feeds()returns them, soretire_group("davewiner")as written woulddrop_managedthe 11 without files, deleting their stored entries.unmanage(src/db.rs:1321) exists for exactly this and was never applied to them.At startup, unmanage any managed row that has its own config entry, then retire every group whose parent is not in config. Copy
state.dbaside before deploying it. (src/main.rs,src/db.rs)