-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Torznab API result sort order #185
Comments
Those extra channel elements appear to be part of the RSS spec, rather than the Torznab or Newznab specs: channel / pubdate:
channel / lastBuildDate:
It doesn't look like either is being set properly though. |
Regarding the torznab results order, it does appear to be using the latest found torrents internally. You can turn off the DHT crawler and the results in the web UI and the Torznab query should then eventually match once it's finished processing what it has, as long as nothing new is being added. |
@binhex Thank you for the PR. Let's hope that will get merged. |
Sorry for the delay, have added a comment on the PR:
|
Is your feature request related to a problem? Please describe
I noticed that Sonarr is only ever requesting a single page from Bitmagnet when performing a normal RSS sync, and therefore doesn't find anthing.
From the code of Sonarr it looks like Sonarr stops requesting further results from the Indexer when the oldest
publishDate
is older than thepublishDate
of the previous RSS sync.The query that Sonarr performs for a RSS sync is
/torznab/?t=tvsearch&cat=5000,5030,5040,5045&extended=1&offset=0&limit=100
.As far as I can see, the result of Bitmagnets
/torznab
endpoint has no sort order and thepubDate
can contain wildly different dates. I have seen dates ranging from 2019 to 2024 in a single query. The result also doesn't seem to be the latest torrents from the web UI.Describe the solution you'd like
I couldn't find anything regarding a default sort order or any recommendations on the sort order in the Torznab specifications. But to me it looks like Sonarr expects that querying the
/torznab
endpoint would return the latest torrents in descending order. So the firstitem
would be the last updated/added torrent in Bitmagnet. Otherwise the RSS sync of Sonarr can't work properly (I think).Additional context
A sidenote: I have also seen that the
channel
contains apubDate
andlastBuildDate
, both of which haveMon, 01 Jan 0001 00:00:00 +0000
as a value and I couldn't find both of these fields in the Torznab specification for thechannel
. I don't know if Sonarr or Radarr is using these fields, but they don't look right to me.The text was updated successfully, but these errors were encountered: