Closed bytebone closed 2 months ago
After further reading, this appears to be an exact duplicate of #193. Issue description and solution match. I'm left a little unsure if this is a Recyclarr issue to begin with, or something that would have to be fixed in Son/Radarr upstream.
Could you provide the respective verbose log along with the two debug logs you provided? I appreciate the detailed report.
Since there were too many runs in between my initial report and now due to all the testing, those reports were overwritten. So I've reproduced the issue with Sonarr so I can provide the 4 logs.
recyclarr_success.debug.log recyclarr_success.verbose.log recyclarr_fail.debug.log recyclarr_fail.verbose.log
I really can't thank you enough for bringing this to my attention. It took me a while to reproduce this on my side, but I finally determined the issue and have a fix. Let me know if this isn't resolved in the next release!
Is there an existing issue for this?
Current Behavior
The
preferred_ratio
is defined inrecyclarr.yml
, but after syncing, the "Preferred" Value in Sonarrs Quality Settings does not change from "Unlimited". Only when The "Preferred" Value is set to anything lower than "Unlimited" does recylcarr adjust the value properly.The exact same issue applies to Radarr. The steps to reproduce and fix are the same.
Expected Behavior
The "Preferred" value should be set no matter of its current state (unlimited or limited)
Steps To Reproduce
recyclarr sync sonarr
recyclarr sync sonarr
againEnvironment & Versions
Recyclarr Log File(s)
This file is from a run where preferred qualities where set to unlimited and no settings were changed recyclarr_fail.debug.log
After setting the preferred values to a number and re-running, everything was applied, documented by this log recyclarr_success.debug.log
Configuration YAML
Sonarr / Radarr Logs
I checked both Radarr and Sonarr logs and cannot see anything related to failed API queries or other issues in connection with Recyclarr.