mirror of
https://github.com/Prowlarr/Prowlarr.git
synced 2026-03-02 22:57:22 -05:00
[AnimeBytes] Ratelimited during search. #831
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Tooling
Area: UI
Area: Update API
Priority: High
Priority: Low
Priority: Medium
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
lidarr-pull
radarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Prowlarr#831
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @lflare on GitHub (Apr 5, 2023).
Originally assigned to: @bakerboy448 on GitHub.
Is there an existing issue for this?
Current Behavior
The current
masterbuild of Prowlarr triggers the ratelimit enforcement action of AnimeBytes too frequently. This seems to be caused by a change made to the site about 12 hours ago from this bug report, (5th Apr 4PM GMT).Officially stated on the wiki, the API endpoint
scrape.phphas a rate limit of 1 request every 10 seconds, though enforcement action such as returning a 429 only applies past 3 requests every 10 seconds.This somehow trips up accompanying applications like Sonarr resulting in complete search/scrape failure.
Expected Behavior
Perhaps Prowlarr can have some kind of throttling mechanism, to delay or slow requests down to 1~2 requests / 10 seconds? Even better, perhaps configurable on a per-indexer scale?
Steps To Reproduce
No response
Environment
What branch are you running?
Master
Trace Logs?