-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Missing results in Jackett (search : manual and auto) #10733
Comments
URL when searching on ygg: URL when searching through Jackett (using default indexer settings): Both return 346 results. The difference is just that the latter is sorted by date (which you can change in the indexer's settings). We're just retrieving the first page of results (twice, due to #9114 - @xfouloux was that unavoidable? We end up with most/all results duplicated), hence why there are results not included. While we can increase the number of pages retrieved, due to the current setup we'd be requesting 4 pages instead of 2, and still only get 100 unique results - increasing search times for users, and server loads for ygg (which I'm pretty sure are already an issue for them). Does that explain what you're seeing, or was there a different issue? |
Well it's been a long time since we do not request multiple pages on the YGG Indexer i think, hence the 100 result limit If there is a way to detect there is more than 1 page of results, then perform the request to page 2, etc etc, i don't remember if there is something like this possible in YML My pull included the fix about French 'Saison' (season) word to be matched on search, but because of YML indexer limitation, i had not found any other way than doing a second search with a regex replace of "Season" by "Saison" and still a normal search with Season word, then bunch of regex for the results to display "Season" everywhere. Unless someone find a better way, or do it as a C# indexer, there will always be issues :( Or maybe the jackett core could be having a remove duplicate function ? |
In any case, i remember that we removed the multiple pages, because sonarr, radarr and such should be precise enough to not make a request that would return lots of results to YGG, but well it could i guess, especially for animes It really need a big rework in C# someday |
Yea, the request for the second page Though we could change it so at least the keywordless search gets the second page, no duplicates:
I'll test it in a bit. EDIT: yep, that worked. Will have another look at the saison fix, but I very much I'll get anywhere. |
I've not changed anything for the repo just yet, and when I do it will only affect keywordless searches (what Sonarr/Radarr/*arr use to check for newly posted torrents), not keyword searches. I'll post when the commit is done, and again when the new stable build is out. Feel free to try out the above if you want, just edit yggtorrent.yml from:
to:
and restart Jackett. |
Results on sonarr for example : some of the missing results from the tracker for this example |
Open the search for ygg in Jackett, don't type anything in the query box, and click the search button. This should show the same results as the first two pages on ygg when you perform a keywordless/empty search (sorted by date). Nothing has changed when using keyword searches (e.g. Supernatural). If you don't need the saison fix, you can just use this instead of the current second path:
You'll either have to change this with each update to Jackett or create a copy of the .yml file in /config/cardigann/definitions/, with that line edited, change the name and id as well, then use this new indexer in Jackett (you can find more details here, just ignore the bits about Docker - #10646). Doing so though will mean that you'll have to keep an eye out for any updates to the file and apply them yourself/repeat the above - https://github.com/Jackett/Jackett/commits/master/src/Jackett.Common/Definitions/yggtorrent.yml |
Because multiple thinking minds can do much better things =) ! Here is what i propose : If there is no keywords, it returns 4 pages of results (200)
Working fine, yeah there will be duplicates sometimes when doing a Keyword search, and it's unavoidable. But it doesn't break anything (maybe sonarr when manually sorting sometimes, and well, for radarr it will do 4 times the same search :/ )
Think it's a good alternative @ilike2burnthing ? Keyword searchNo KeywordsProof SearchYou can see it works fine searching for example for "Battlestar Galactica S1" one of the torrent name is "Battlestar Galactica Saison 1 [720P] [FR] [ENG]" and jackett displays it correctly "Battlestar Galactica S01 [720P] [FR] [ENG]" among the other results |
Better, for example : And there is still some "problem" -> In any case, thanks a lot for your (lovely) help ! :) |
hummmm you are using the Beta search engine check option, i get 113 results too when using it. The Beta search will search for anything that have 'Supernatural' in it in YGG website, it is not a jackett issue, ygg take the search term and remove everything that looks like episode number and such, doing a wider search Test without the option checked, and see if it fits you better if you want to try on the website, change /engine/ by /new_search/ in the URL
Also on your second screenshot, you are searching for s5 in jacket and s05 in ygg, it can return different stuff Regards |
Thanks a lot ! 🥇 |
I had considered this, but had a few reservations:
|
Yeah there is no perfect solution unfortunately without doing a C# indexer :/ |
is there any way to hack this, and make the if else do something on keyword search and fail (bad url) when keywordless ? |
Changing If it doesn't result in errors in Jackett's logs (which I imagine it will), then it could be a possible hacky way to only pull 2 keywordless results pages (i.e. the vast majority of any traffic we would be causing), but still get 4 for keyword searches. |
My problem now, is that, Radarr and Sonarr are saying quite often that the indexer (ygg) failed due to errors, but when I test it, it comes back to normal. Could you have a solution, perhaps ? Or a way to auto-test the indexer when there is a failure ? |
I'd suggest asking over on https://forums.sonarr.tv/ but it will retest in the sense that it will keep trying to use the indexer every 15/30/60mins or whatever you have it set to. If errors continue for extended periods of time, it will increase the delay - https://wiki.servarr.com/Sonarr_System#indexers_are_unavailable_due_to_failures |
it's an issue with the captcha not being solved all the time i guess via flaresolverr, and then it goes into failed state :/ |
@WoisWoi and for whoever wants to do this, here is how you can do a testall indexer via a bash script (i do mine every hours to keep indexer OK, especially YGG)
|
Environment
OS: Linux Ubunta Server 20.04 (x64)
Jackett Version: v0.17.197
Last Working Jackett Version: v0.17.197 I guess
Are you using a proxy or VPN? no
Description
When I do a research with Radarr, Sonarr or manually directly into Jackett, results are missing (compared to the one I get by searching directly on the tracker). In this case, YGGTorrent is the tracker and I'm using FlareSolverr with the hcaptcha-solver.
Log
"2021-01-04 23:37:23.6561 Info Manual search in yggtorrent for Supernatural => Found 100 releases "
No error(s) on the search. Is there a limitation to 100 releases found ? I found 346 results on the tracker with the same request.
The text was updated successfully, but these errors were encountered: