Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #19883
Closed (moved) (moved)
Open
Issue created Aug 10, 2016 by Andrea Shepard@andrea

Maintain CONFIRMED_GUARDS per new guard plan

New guard plan summarized at https://lists.torproject.org/pipermail/tor-dev/2016-July/011234.html

  1. Maintain CONFIRMED_GUARDS
  • Add guard to CONFIRMED_GUARDS when circuit succeeds
  • Fill in state info for each confirmed guard (confirmed_on_date, etc.)
  • Migration from old state format to new
  • Thoughtworks unittest: test_used_guards_parse_state()
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking