Enable debug logging in SickRage settings, reproduce the error (be sure to disable after the bug is fixed)
Branch: master
Commit: de056c2380cb140bf8430a1ac4569899b3b44a52
Version: v2017.03.01-1
What you did: I do not use search providers (NZB or Torrent). I use post processing via mounted seedbox
What happened: Every hour/few hours I get a warning message saying that No NZB/Torrent providers found or enabled
What you expected: That no warnings are issued as the program is getting the releases via post processing. If they do need to have a warning, just do one. Don't have the warnings over & over.
Logs:
2017-03-02 09:14:53 SEARCHQUEUE-DAILY-SEARCH :: No NZB/Torrent providers found or enabled in the sickrage config for daily searches. Please check your settings.
Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked
Please make sure you also read how to create an issue and followed all of the steps.
The title should describe your issue. Having "SR not working" or "I get this bug" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.
Sometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.
Thanks!
@miigotu
Change this to a logger.WARNING, or add an option to disable daily search (set freq to 0),
or something else?
It's already warning, change it to info.
Yep that's what I meant... Copied and forgot to change.
Add it to our other PR =p
Hi, thank you for the quick reply, I appreciate it 馃憤
So are you planning on changing this one from a warning to a log entry?
Yep, it would show up in the logs as info and not as a warning.
However, because most users want to use this feature (daily search),
we will show a different message, similar to the available update message.
Alright, I am not exactly sure how it will show up, but, I look forward to see what the difference will be :)
Could it be dismissed permanently for users that don't want to use the feature?
Yes, developer = 1 in the ini. It's really a pointless way to use SR, so it isn't going to be some elaborate customized/supported feature. We will give you a way to avoid the warnings, that's all.
If you want something just to rename and move files there are better options. Sickrage is an all in one solution, you don't need anything else other than a download client.
Well for me it is a good solution. It downloads the files (copies from mounted SB), renames them and sorts them. So it is more than just the download part... It is essentially the same as NZB or Torrent, they are just downloaded via a different method.
Just don't expect a whole lot of work/support from us to accomodate using SR in a way that it is not intended to be used. We will give you a way to avoid the warnings, that's all.
I just updated, thanks for the new build and removing it from the warnings part. The only problem is the big box that comes up keeps coming back after you press the dismiss button. As soon as you reload the page or go to another tab, it comes back as big as ever. Can it be changed so that it remembers you have dismissed it please
I told you, stop SR, change the developer setting to developer = 1. No further changes for this usage will be made, because literally no-one else uses this sort of setup.
@DrSpaldo You were right about the message.
It wasn't supposed to keep showing every time you refreshed the page or went to another tab.
I fixed that in https://github.com/SickRage/SickRage/pull/3298/commits/794ca672fb7c99714c90aa658106df768cfa08ab.
When that merges to master you will be able to restore developer = 0 and you will only see the message every SickRage (re)start.
And when you save providers settings ^
@miigotu there is no need to be like that. I am a user and I know others that use it in this method (it is on google search), so I am not the only person in the world....
I raised a valid issue about the warnings, the pop up is a much better method regardless of how SR is being used. It isn't a bad thing if we (the small amount of users using the mounting method) can use SR as well as the intended/normal method is it? The issue with the new change (that the bar wont dismiss correctly) is a valid one. Regardless of why the new change was made, you still want it to be functioning correctly don't you?
@sharkykh thank you for your help and quick reply/action. It is appreciated :)
Not really interested in spending too much time on something that benefits only a very small group of users.
Since it's fine now, have a good day.