Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check cache for candidates when searching using backlog search. #5816

Merged
merged 14 commits into from
Dec 8, 2018

Conversation

p0psicles
Copy link
Contributor

@p0psicles p0psicles commented Dec 2, 2018

  • PR is based on the DEVELOP branch
  • Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review
  • Read the contribution guide

fix #5582

This should be extensively tested before merging.

ASIS: In each backlog for every episode search, we check the cache if we get anything back. If so, we dont bother searching the provider. This makes the searching process heavily dependent on the Daily/RSS search.

With this change, we also check if the results from cache, include any candidates, where we also check quality, required words, release groups, etc.

If the results do not have any candidates, we start a search for the provider.

@ghost
Copy link

ghost commented Dec 2, 2018

DeepCode analyzed this pull request.
There are no new issues.

@p0psicles
Copy link
Contributor Author

@medariox let's refine this PR some more and then merge to develop. The user can only test master/develop as he is running on synology.

@p0psicles
Copy link
Contributor Author

Im pretty much done with this. Tried to make it a little bit more DRY. And ran different searches.

@medariox medariox merged commit 3ee452a into develop Dec 8, 2018
@medariox medariox deleted the feature/check-cache-for-candidates branch December 8, 2018 19:50
@medariox medariox added this to the 0.2.14 milestone Dec 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants