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

Closed (moved)
Open
Opened Apr 28, 2011 by Roger Dingledine@arma

setconf clears bridge descriptor refetch timers

I was looking at #2355 (moved)'s hopes of refetching bridge descriptors as soon as the bridge list changes. My plan was to simply call fetch_bridge_descriptors(now) from inside options_act() once we've cleared and reparsed the bridge lines.

Then I realized that clearing and reparsing the bridge lines resets the timers. So currently Tor clients that use bridges will refetch all their bridge descriptors an average of 30 seconds after each setconf. Bug.

Better behavior might be to leave parsed bridges alone if they're the same.

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