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

Closed
Open
Created Sep 23, 2012 by Karsten Loesing@karsten

(relays|bridges)_published in Pyonionoo should not depend on relays/bridges contained in result

Right now, (relays|bridges)_published in Pyonionoo contains the latest timestamp of relays/bridges contained in the result. If there are no bridges/relays, the respective published time is 1900-01-01. If the returned bridges/relays were not offline for a few hours, that time is returned as published time.

I admit that the Onionoo protocol specification was imprecise there by specifying what's currently implemented in Pyonionoo. But the current Onionoo behavior makes more sense for clients. Tweaked the specification.

The (relays|bridges)_published fields should contain the timestamps when the last consensus known to Onionoo/Pyonionoo became valid and when the last known bridge network status was published.

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