Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #27212

Closed (moved)
(moved)
Open
Created Aug 20, 2018 by teor@teor

Why do bridges run the retry_dns callback?

In a4fcdc5dec, the following roles seem inconsistent:

+  CALLBACK(retry_dns, PERIODIC_EVENT_ROLE_ROUTER),
+  CALLBACK(check_dns_honesty, PERIODIC_EVENT_ROLE_RELAY),

It's probably unrelated, but I don't think clients write stats:

+  CALLBACK(write_stats_file, PERIODIC_EVENT_ROLE_ALL),

(Do onion services write stats?)

From https://trac.torproject.org/projects/tor/ticket/27080#comment:4

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking