A failing YouTube feed is asked again hourly for a day (#386)
#382's retries run (each failing fetch takes the two seconds) and still end 404: YouTube fails about 70% of feed reads from Tower, in streaks longer than seconds, for ?user= and ?channel_id= addresses alike (142 and 68 failures in 7 days across 26 and 13 feeds). The 39 YouTube channels are catalogue feeds nobody subscribes to, read once a day, so each missed about 5 days in 7. due_at now waits at most an hour for a YouTube feed in the first day of a run of failures. A channel gone for good costs 24 requests, then backs off as any feed does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -18,7 +18,7 @@ pub use artwork::{is_image, prefer_https, site_icon};
|
||||
pub use category::{categories, category_path};
|
||||
pub use discover::{expand_input, find_feed};
|
||||
pub use failure::{Failure, explain_failure, failure_kind, is_temporary_lookup_failure};
|
||||
pub use fetch::{FEED_SILENCE, FEED_TIMEOUT, FETCHED_BYTES, FETCHES, Fetched, fetch};
|
||||
pub use fetch::{FEED_SILENCE, FEED_TIMEOUT, FETCHED_BYTES, FETCHES, Fetched, fetch, is_youtube_feed};
|
||||
pub use jev::{JEV_URL, classify};
|
||||
pub use outlines::{collect_outlines, is_opml, opml_title, parse_opml, read_opml};
|
||||
pub use parse::{Enclosure, Entry, ParsedFeed, markdown_html, parse, same_file_key};
|
||||
|
||||
Reference in New Issue
Block a user