#25002: Make data and results from Onionoo deterministic -----------------------------+------------------------------ Reporter: iwakeh | Owner: metrics-team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Metrics/Onionoo | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------+------------------------------
Comment (by karsten): Replying to [comment:9 iwakeh]: > Replying to [comment:8 karsten]: > > Replying to [comment:6 iwakeh]: > > > Maybe, also use the valid after timestamp for the value in file `out/update` or remove the file? > > > > That might even be part of #16513. We cannot remove that file, because we need it for updating the index in the server part. But we could use something else as timestamp than the current system time. Not sure if valid-after timestamp is the best choice, because we have two such timestamps for relays and for bridges. Maybe we could use the last- modified time of `status/summary` here. Untested, just an idea. > > Last modified time of `status/summary` is not deterministic across instances. What about using the latest time of the two valid after timestamps? This would sort of synchronize Onionoo with 'Tor time'? Yes, sounds good! -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25002#comment:11> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs