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

Closed (moved)
Open
Opened Sep 17, 2019 by Roger Dingledine@arma

relay-search lists flakey as down for an hour or two, when it's never been reachable

https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F is marked as offline, and the "downtime" section varies over time but it always seems to be more than one hour and less than two hours.

That's because the bridge firewalled its ORPort, so it never gets the Running flag from Serge, so bridgedb won't give it out. Makes sense -- it is the snowflake bridge, so it receives its connections via the bridge-side snowflake proxy, not direct to the ORPort.

But metrics seems to have hit an edge case: it does something weird when it has no known "time it was last up" value.

(Not a big deal, but it's been sitting in a tab for some days now and I figured I should file the ticket.)

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