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

Closed (moved)
Open
Opened Oct 08, 2009 by Tom Lowenthal@flamsmark

'Stable' flag assignment inconsistant

Looking at a consensus document [though I used torstatus.all.de for ease of sorting data] it seems that the 'stable' flag is not being consistently assigned.

According to the v3 directory specification at https://git.torproject.org/checkout/tor/master/doc/spec/dir-spec.txt , routers with a weighted MTBF more than either the median or seven days should be marked stable, and MTBF data more than a month old shouldn't be that relevant when assigning the flag. Since the median uptime is about 3 days, one should roughly expect that any router with more than 30 days of uptime (and which are still valid) should have the stable flag. However when relays are sorted in order of uptime, several apparently-longrunning routers do not have the flag.

Since this data is liable to change as relays go up an down, here are some noted not-'stable' routers at the time of writing. The routers have uptimes more than a month, so their (correctly) weighted MTBF should certainly be more than a week, and more than the median, about three days.

wie6ud6be - 148d anonymde - 112d torpfaffenederorg - 110d rentalsponge - 70d xhyG5r96QGlRqL - 57d niugnip - 56d oeiwuqej - 49d gremlin - 42d editingconfigishard - 39d

[Automatically added by flyspray2trac: Operating System: All]

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