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 was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Delete rulesets which are all gone from DNS #10595
@koops76 Thank you for helping in resolving this issue. Please note that not all the domain listed in the above are completely gone from DNS. Occasionally, you might want to update a ruleset instead of deletion.
Number of occurrence of Could not resolve host: == number of non-wildcard target
The command I use can be modified to match rules failed the fetch test twice and Could not resolve host: == 2 * number of non-wildcard target, but I am afraid that the number of false results is going to be much more significant.
As for #10729, I guess it is because of the improper indentation (with space)
@cschanaj I merged your recent deletion PRs but from #10516 (comment) it sounds like full-fetch-test should get rid of these rulesets automatically, so you don't need to submit PRs to delete them. What do you think?
Activity
cschanaj commentedon Jun 26, 2017
@koops76 Thank you for helping in resolving this issue. Please note that not all the domain listed in the above are completely gone from DNS. Occasionally, you might want to update a ruleset instead of deletion.
Bisaloo commentedon Jun 27, 2017
@cschanaj, any idea why your script didn't pick up #10738, #10732, #10729?
cschanaj commentedon Jun 27, 2017
@Bisaloo For #10738, #10732 The items from the list only include ruleset which
Disabled by https-everywhere-checkeronce onlyCould not resolve host:== number of non-wildcardtargetThe command I use can be modified to match rules failed the fetch test twice and
Could not resolve host:== 2 * number of non-wildcardtarget, but I am afraid that the number of false results is going to be much more significant.As for #10729, I guess it is because of the improper indentation (with space)
cschanaj commentedon Jun 27, 2017
Let's wait for the discussion in #10516 (comment) complete before submitting new deletion PRs.
jeremyn commentedon Dec 14, 2017
@cschanaj I merged your recent deletion PRs but from #10516 (comment) it sounds like
full-fetch-testshould get rid of these rulesets automatically, so you don't need to submit PRs to delete them. What do you think?