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
  • #34213

Closed (moved)
Open
Opened May 14, 2020 by Karsten Loesing@karsten

Replace TorCtlParser with OnionTrace's control log parser

Similar to our plan to use TGen's analysis.py instead of OnionPerf's in #33974 (moved), the idea would be to avoid keeping our own copy of a Tor control even log parser in OnionPerf.

This work should start with an analysis how much work this is going to save in the long run, and whether that justifies adding another dependency.

Feel free to adjust estimated points before starting to work on this if 2.0 doesn't make any sense.

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