Repository navigation
Automations: a rule that matches nothing runs on every 20 s scan, ignoring its interval (and reloads cross-seed file lists each time) #3785
DescriptionA rule's intervalSeconds only holds when the rule matched a torrent. A rule that matches nothing is treated as due again on the next 20 s scan, forever. For delete rules in the "preserve cross-seeds" (or "include cross-seeds") mode, every scan then loads the file lists of every cross-seed group on the instance. With the 5-minute file cache, that turns into a burst of torrents/files requests to qBittorrent every ~320 s. Steps to reproduceSetup Turning both rules off stops the bursts. Expected Cause (from the source) Scans run every 20 s (ScanInterval: 20 * time.Second, line 600). Impact EnvironmentLog linkNo response Relevant logsNo response Checklist
|
Replies: 2 comments
Triage NotesWhat we have established so far:
What we still need from you (@lardbinvalence):
|
|
Thanks, you're right, and my original cause was wrong.
Suggestion:
|
Triage Notes
What we have established so far:
intervalSecondshas passed since its last stamp inlastRuleRun.rulesNeedCrossSeedFilesthen loads cross-seed file lists for every eligible rule in a cross-seed-aware delete mode. Your reading of this part is correct.applyRulesForInstance, "matched" means something narrower than the report says. A rule gets its stamp when its tracker pattern (selectMatchingRules/matchesTracker) matches at least one torrent that was not processed in the last 2 minutes. The conditions do not count, soIS_UNREGISTERED = trueand the o…