Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #33570

Closed
Open
Created Mar 09, 2020 by juga@jugaMaintainer

Correct the relays to keep after retrieving new consensuses

When removing the old consensus timestamps, the oldest date is calculated with timedelta without passing seconds, which was taking it as days, making the oldest date very far in the past. Recent timestamps are calculated as greater than the oldest date, instead of minor, what would make to store many timestamps. The most recent timestamp for a relay, was not being took into account, because the router status was being updated after updating the timestamps.

Assignee
Assign to
Time tracking