Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • N Nebulo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PublicAndroidApps
  • Nebulo
  • Issues
  • #197
Closed
Open
Issue created Nov 14, 2019 by Daniel Wolf@dwolfMaintainer

Fix behavior of the local resolver

The local resolver has been optimized, but still has problems:

  • it doesn't clear cache when a rule changes
  • it does not detect when a list is deactivated, but not removed

Additionally, it should pre-fill the whitelist cache with non-wildcard entries, as those are the heaviest to query. With the same reasoning the whitelist cache should be bigger.

Both wildcard types (whitelist & normal) should be checked after non-wildcard rules. All caches should be checked first.

Assignee
Assign to
Time tracking