Conversation
|
Important Review skippedToo many files! This PR contains 243 files, which is 93 over the limit of 150. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (243)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
f6c451e to
b8b1a22
Compare
…s, dashboard adapters)
The old nzbFailover.ts was nzb-only; this overhauls it into a generic failover chain (FailoverContentType = 'usenet' | 'debrid') that also handles debrid and supports parallel queuing / staggered races (parallel, staggerMs, preferredGraceMs, maxWaitMs).
…tual failing volume
…real-world codec aliases
…en applying to streams
…lity (#1070) Cloudflare classifies requests by the URL path extension alone: a stream URL ending in /<filename>.mkv is treated as a cacheable file type, so on every cache miss (guaranteed, as the route sends no-store) the proxy requests the entire file from origin and never forwards the client's Range header. Every seek then costs a full-file pull, playback stalls, and abandoned pulls pile up as orphaned full-file readers. Dropping the filename segment makes Cloudflare treat the response as dynamic and pass Range through verbatim. The route already accepts both forms, so previously minted URLs keep working; players still receive the real filename via Content-Disposition. Co-authored-by: Viren070 <viren070@protonmail.com>
No description provided.