Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Re-activating rulesets disabled by https-everywhere-checker with only one problematic domain #12677

Closed

Description

No description provided.

Activity

  1. cschanaj commented on Sep 22, 2017

    @cschanaj
    Collaborator

    a dirty way to find such ruleset could be

    $ grep -l 'failed ruleset test' *.xml | while read filename; do if [ $(egrep -c '^Fetch error:' $filename) -eq 1 ]; then echo $filename; fi; done

    with some false result for fetch-error only.

  2. ghost closed this as completedon Sep 22, 2017
  3. ghost reopened this on Oct 20, 2017
  4. ghost closed this as completedon Oct 20, 2017
  5. cschanaj commented on Oct 21, 2017

    @cschanaj
    Collaborator

    Personally, I think the filename list is too huge to be maintain manually in a issue. So, I will keep a list of filename and hash in simple-default-off-list.txt which can be automatically cleanup by a script.

    Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions