Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #22512

Closed (moved)
Open
Opened Jun 06, 2017 by Karsten Loesing@karsten

Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

Todo derived from the discussion in comments 1 to 4:

Add keywords for all descriptors to Key enum. Use a one letter prefix for keywords from non-Tor data sources. First step: determine the best letter for each non-Tor source.

Original summary: We recently introduced the Key enum with keywords contained in relay descriptors, sanitized bridge descriptors, and sanitized bridge pool assignments. We did not include keywords in exit lists and Torperf measurement results, and in retrospect we should have excluded sanitized bridge pool assignments there.

The reason why each data source should have its own enum is that naming conventions might vary in terms of upper/lower case and word separators. For example, Tor descriptors use lower-case-keywords, exit lists contain CamelCase, and Torperf/OnionPerf use ALL_UPPER_CASE_WITH_UNDERSCORES. There could be conflicts for keywords like source vs. SOURCE.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#22512