Jackett v0.22.43 throws exceptions when used with Sonarr about jackett HOT 18 CLOSED

Just pushed a fix for the issue, for now to bypass the issue you can disable the cache until the next release.

from jackett.

should we tag a new release?

Oh, this actually means publish a new release ! I completely misread this, and went looking in the history to see if between v20 and v21, v19 and v20, and v18 and v19 if we had set a special release tag, and not found anything ;-D
Sorry about that.

from jackett.

I only wish that were true more broadly (see basically every YGGtorrent issue here and on FlareSolverr, along with the 2k+ other duplicate issues here).

Okay . . . very fair lol ;-)

from jackett.

v0.22.56

from jackett.

Care to explain if all indexers throw that error or only a few? If so, care to name them?

from jackett.

All indexers are down. I use Anime Tosho, Nyaa, BakaBT and SubsPlease. Jackett log is spammed with multiple occurences of the above error.

from jackett.

I need you to go to Jackett's UI and click on test and tell which ones are throwing errors, because I can't reproduce with those few indexers.

from jackett.

Tests work without issues in both Jackett ans Sonarr. Error occurs when in Sonarr i press the RSS Sync button in the main window.

from jackett.

Provide trace logs from Sonarr then.

Go to Settings > General > Logs level to trace and then reproduce the issue, after upload the contents of sonarr.trace.txt from system > log files to https://privatebin.net

from jackett.

Below you can find the requested logfile:

https://privatebin.net/?ed54a27ea02e28db#9mz6rDqL7vE5u2yZ37wgZfUYYym4o2LMQ9zbCRHoN2XM

from jackett.

Thanks, can finally reproduce.

from jackett.

I have the same problem. In Jackett all indexers work but when I sync with Sonarr/Radarr the problem occurs. If I restart Jackett the sync works the first time but as soon as I try again the problem comes back.

from jackett.

Thanks, it works !

from jackett.

@garfield69 @ilike2burnthing should we tag a new release?

from jackett.

should we tag a new release?

we've not done so in the past.

from jackett.

Sorry, just getting back online now. We've done off-schedule hotfix releases for breaking bugs in the past (granted, I think only 2 or 3 in my few years here). Had I been online 9hrs ago I would have said yes, but as there's only 6 hrs to go, we're not being flooded by issues, and the temporary workaround is 'disable cache', I think we're fine to wait.

from jackett.

Possibly you are not being flooded by issues because people like me search before creating an issue. Given the severity and the troubleshooting a person has to go through before getting to this issue a hotfix would've been much appreciated.

from jackett.

Possibly you are not being flooded by issues because people like me search before creating an issue.

I only wish that were true more broadly (see basically every YGGtorrent issue here and on FlareSolverr, along with the 2k+ other duplicate issues here).

a hotfix would've been much appreciated

As I said, had I saw the question half a day ago, it would have happened.

from jackett.