-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Some Indexers don't return all results for id based searches #425
Comments
This is most likely a limitation of the tracker no supporting both id and text to be used in the same time. But Prowlarr works fine with multiple parameters. |
Hmm I did some more snooping around and you seem to be at least mostly right. So it seems that it indeed is only an issue when an id is provided. Checking in the search box of the site of the first indexer seems to prove it. However this doesn't fix that sonarr will automatically use the id parameter if prowlarr reports that it's supported by the indexer. Is there any possible fix that can be done? |
You can snoop the Indexers repository for the definitions for you indexers. For THERARBG you can check it here where the condition is either one of them, not both in the same time: Indexers/definitions/v9/therarbg.yml Line 71 in 4861ac8
These are just search limitations of the sites. |
I don't know if Prowlarr should disable id based searches for tvsearch same as Jackett... |
This was disabled in Jackett with the comment While some indexers would need reworked to support this, many are already set up to work with that simple setting change, e.g.: (linking to the Jackett version as it seems rotorrent.yml is missing here) To save managing more differences between Jackett and Prowlarr definitions, this would probably be best implemented on both at the same time (I say that knowing that I won't be the one doing the work 😛). |
TBH considering the possible issues with the release titles the different languages, I would prefer id based searches returning all seasons instead of no results at all. |
The issue was that for trackers which only returned 40 or 20 results per page, even if we grabbed 2 pages there was still a chance that relevant results wouldn't be returned (e.g. a series has 6 seasons, user wants S02E13, but that doesn't appear until page 4 as results are sorted by descending time). However, because any results were returned, Sonarr doesn't perform a title search, and therefore Sonarr finds no relevant results. Even a tracker that returned 200 results still wouldn't show everything for a big enough series. We have |
Seems overkill, we can simply add or remove imdbid from tvsearch caps. 🤔 |
~200 indexers currently list imdbid TV support, not all of which we have access to, so that seems like a lot of work as well. I'm not sure which would be more. I'm also not sure if there are any other (non-arr) projects, or even just scripts, which rely on imdbid TV search, but don't check |
I vote for the disable by default and do a new flag to enable it like was planned / not implemented for jackett. perhaps we can use the # engine tag to help facilitate more bulk changes? imdbid only for tv often causes more issues historically from a support view |
I disagree. 👺 |
Soooo @mynameisbogdan @ilike2burnthing where we going with this? |
Status quo feels like the right thing. |
I wouldn't be the one implementing it, so I'll take Bogdan's lead. Maybe we could add a comment to the indexers, for those trackers which technically support IMDB ID search for TV releases, but not with season and/or episode information? e.g.: modes:
search: [q]
tv-search: [q, season, ep] # tracker imdbid search cannot be used with season/ep
movie-search: [q, imdbid]
music-search: [q] |
Seems reasonable to me |
Related - Prowlarr/Prowlarr#611 |
What do you mean, a way to use |
Yea, my suggested So for a tvsearch imdbid search, if: So name: "{{ .Keywords }}"
seasonNumber: "{{ .Query.Season }}"
episodeNumber: "{{ .Query.Ep }}"
imdbId: "{{ .Query.IMDBIDShort }}" and this Luminance example: searchtext: "{{ if .Query.IMDBID }}{{ .Query.IMDBID }}{{ else }}{{ end }}"
title: "{{ if .Keywords }}{{ .Keywords }}{{ else }}{{ end }}" whereas in this example we'd leave it to the default of search_type: "{{ if .Query.IMDBID }}imdb{{ else }}title{{ end }}"
search: "{{ if .Query.IMDBID }}{{ .Query.IMDBID }}{{ else }}{{ .Keywords }}{{ end }}" |
bumpy bumpy bumpy for Bogdan thoughts |
Is there an existing issue for this?
Current Behavior
When using parameters to do a search, not al parameters are used in the link used to grab the results.
I'm not sure how I can explain it better so I'll just give an example:
When I search for a season of a show, sonarr searchs via prowlarr using the parameters: {ImdbId:tt1520211}{season:2}.
Those parameters get parsed correctly, as they're visible in prowlarrs log entry:
2024-04-01 23:02:48.7|Info|ReleaseSearchService|Searching indexer(s): [TheRARBG] for Term: [] | ID(s): IMDbId:[1520211] for Season / Episode:[S02], Offset: 0, Limit: 100, Categories: [2000, 5000, 5080]
However, when I go to the history tab and check the link it used to grab the results I see this:
https://t-rb.org/get-posts/order:-se:category:Movies:category:TV:category:Anime:category:Documentaries:keywords:tt1520211:paginate_by:100:format:json/
which only includes the ImdbId but not the season. This causes the results to vary wildly, they're all the right show of course but not a single one of the 100 results was of the correct season, which causes sonnar of course to fail completely.
If you click on the indexer you can see that the Search Capabilities do say that it supports those parameters, which makes sense because sonarr uses those parameters automatically for that indexer, and not for others that don't support it. Which makes it so only indexers who don't support it work correctly.
Reordering of the parameters has no effect, but removing the ImdbId does cause it to return results of Season 2, but this time of completely random shows.
I looked through the settings of sonarr and prowlarr but couldn't find any settings related to the parameters or Search Capabilities so I figured the next most sensible thing was opening a bug report.
Expected Behavior
When multiple parameters are given they should all be added to the link prowlarr generates.
Steps To Reproduce
Environment
What branch are you running?
Master
Trace Logs?
https://gist.github.com/ThatIcyPolarBear/e969e1e63cb02cfaeb6f673bac5dffa5
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
trace
- that are relevant and show this issue.The text was updated successfully, but these errors were encountered: