p0ps

Sounds like a good approach @duramato @medariox?

Yeah but its good to have a list of working trackers that we dont have to maintain right? I know @duramato always keeps track, but still.

Could you enable debug logging, and try to reproduce the error? My guess is, the file is already in use by another process. Or maybe file access issues.

Don't use download handler with Synology download station.

Just this warning is pretty useless. Well need a surrounding debug log. Please also fill in the issue template

Regarding keeping the deps up2date. We already spend a lot of time on that. So, its not realistic to have them up to date all time. Just something we have...

Only thing I can do about It is change the log to info. Other than that I can remove the addic7ed provider. But it is working for some users.

Ow really. Yeah that shouldn't

Is this a format that can safely be applied to all torznab providers. Does this also works with prowlarr? Btw we recommend the usage of prowlarr above jackett.

The issue here is that medusa doesn't have a specific type provider for jackett or prowlarr. It uses the newznab and torznab specs. So any change I make here to...