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

Closed (moved)
(moved)
Open
Created Jun 11, 2017 by Roger Dingledine@arma

AssumeReachable 1 on a relay doesn't make it publish quickly

According to the man page for AssumeReachable,

           If set
           to 1, don’t do self-reachability testing; just upload your server
           descriptor immediately.

But sometime between then and now, perhaps when we messed with the "we don't publish until dirport is reachable too" logic, we lost that 'immediately' property.

It looks like now we don't do some of the checks, and also we don't publish immediately, and then we end up publishing "after a while" when some other condition triggers to consider publishing.

I'm guessing the fix could be as simple as "when we bootstrap to 100%, check if assumereachable, and if so trigger a publish then."

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