Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • O opentrafficshaper
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • opentrafficshaperopentrafficshaper
  • opentrafficshaper
  • Repository
  • opentrafficshaper
  • opentrafficshaper
  • plugins
  • configmanager.pm
Find file Blame History Permalink
  • Nigel Kukard's avatar
    An undefined value shouldn't cause a negative match result · d7f0eb42
    Nigel Kukard authored Mar 06, 2018
    We may or may not have a candidate attribute, if we don't we should just
    ignore it rather than count it towards a negative match.
    d7f0eb42