rays
245fa79fbf
YouTube answers some requests for a channel's feed with a 404 or 500 in tens of milliseconds, while the next request for the same feed, or another channel's 200 ms later, reads. Checked once a day, the 39 YouTube channels in the catalogue missed most days: 178 failures in the week to 2026-11-04, against 74 in the ten days before, and all 39 read from Tower when asked by hand. feed::fetch now asks a youtube.com/feeds/videos.xml address again, up to twice, a second apart, when it answers 404 or 5xx. Other hosts' 404s are real and are not retried. tokio moves from ipx-feed's dev dependencies to its own, for the sleep; both services build it already. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
26 lines
508 B
TOML
26 lines
508 B
TOML
[package]
|
|
name = "ipx-feed"
|
|
version = "0.0.0"
|
|
publish = false
|
|
edition.workspace = true
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
atom_syndication.workspace = true
|
|
chrono.workspace = true
|
|
http.workspace = true
|
|
hyper-util.workspace = true
|
|
opml.workspace = true
|
|
pulldown-cmark.workspace = true
|
|
quick-xml.workspace = true
|
|
reqwest.workspace = true
|
|
rss.workspace = true
|
|
serde_json.workspace = true
|
|
tokio.workspace = true
|
|
tower.workspace = true
|
|
tracing.workspace = true
|
|
url.workspace = true
|