You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2024. It is now read-only.
when a plugin has 3(maybe more but not as a setting -> too many settings and variables to test and resolve issues) or more errors disable it create a message in the gui
this will also solve hitting indexers / providers / downloaders with wrong credentials ...
but might disable a provider that is just down for a while which means it has to be actively activated again just because the indexer is not reachable for a while
(but is in a sense a monitoring on indexers and providers too)
also send notifications with notifiers
maybe add a recovery scheduler that tries in long intervals (48h) to reach these indexers / providers / downloaders again ... but that would need some kind of cache to know which have been deactivated by the system (not user) ...
either have it use a hidden config or a non persistent memory cache
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
when a plugin has 3(maybe more but not as a setting -> too many settings and variables to test and resolve issues) or more errors disable it create a message in the gui
this will also solve hitting indexers / providers / downloaders with wrong credentials ...
but might disable a provider that is just down for a while which means it has to be actively activated again just because the indexer is not reachable for a while
(but is in a sense a monitoring on indexers and providers too)
also send notifications with notifiers
maybe add a recovery scheduler that tries in long intervals (48h) to reach these indexers / providers / downloaders again ... but that would need some kind of cache to know which have been deactivated by the system (not user) ...
either have it use a hidden config or a non persistent memory cache
The text was updated successfully, but these errors were encountered: