Skip to content
Discussion options

You must be logged in to vote

This was generated by AI during triage.

Triage Notes

What we have established so far:

  • The scheduler checks rules every 20 s. A rule is skipped only while less than its intervalSeconds has passed since its last stamp in lastRuleRun. rulesNeedCrossSeedFiles then loads cross-seed file lists for every eligible rule in a cross-seed-aware delete mode. Your reading of this part is correct.
  • In 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, so IS_UNREGISTERED = true and the o…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by lardbinvalence
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working backend performance automations needs-confirmation Awaiting confirmation before converting to issue needs-info Waiting on the reporter for more information
1 participant