feat(clear-indexer): adds cli argument for clearing indexer stats #650
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmgoodnow
reviewed
Apr 22, 2024
zakkarry
force-pushed
the
clear-failures
branch
from
79ea01d
to
5619fa4
Compare
mmgoodnow
reviewed
Apr 22, 2024
mmgoodnow
approved these changes
Apr 22, 2024
zakkarry
added a commit
that referenced
this pull request
Apr 22, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 22, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 22, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 23, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 23, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 23, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
zakkarry
added a commit
that referenced
this pull request
Apr 23, 2024
this clears all values in the indexer table relevant to enabling the indexer. i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour. has happened enough times that i wish it was available for support. --------- Co-authored-by: Michael Goodnow <mmgoodnow@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this clears all values in the indexer table relevant to enabling the indexer.
i don't think we should advertise this command in docs, but i think it would benefit support when a user doesn't have to clear their entire db to get around a rate limiting from torznab that would otherwise last 24hours but was really only necessary to back-off for an hour.
has happened enough times that i wish it was available for support.