mirrors/arti.git/crates/tor-circmgr/src/timeouts, branch arti-v0.2.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.0 2022-02-09T15:06:53Z Add TODOs on uncertain points about time_since_last_traffic 2022-02-09T15:06:53Z Nick Mathewson nickm@torproject.org 2022-02-09T15:06:53Z urn:sha1:3c342ae5d7ff29b1354ea561d6bba110beb76b2a This edge-case was there even before the migration of 595fe1ab881b94106649, but now it's more explicit and ought to be revisited. Remove the use of Mutex in channel unused_since timestamp 2022-02-08T23:28:45Z Yuan Lyu lyuyuan92@gmail.com 2022-02-08T23:28:45Z urn:sha1:595fe1ab881b94106649f9b19eebedf926d68f1b Only count timeouts when we've seen net activity. 2021-12-20T20:34:17Z Nick Mathewson nickm@torproject.org 2021-12-20T20:34:17Z urn:sha1:efe74e8c9b522cf0e7966be464cd8188f4b9664f This closes arti#256. It makes our behavior match Tor's more closely, though it has a simpler implementation than Tor. I think that the extra complexity in Tor's logic is because we used to record timeouts in the histogram as well as in the success/failure log. fix nightly clippy errors 2021-12-09T11:16:23Z Trinity Pointard trinity.pointard@gmail.com 2021-12-09T11:16:23Z urn:sha1:9753a7ee06d1dad9b9dbaa1653593bb545d4cf59 Use a safer histogram rebuild algorithm. 2021-12-08T15:59:36Z Nick Mathewson nickm@torproject.org 2021-12-08T15:59:36Z urn:sha1:940ab11b80e159ec4fe94734e8245e5350f6ccb9 Our old algorithm could, on some inputs, exhaust RAM. That's not great, since we try to be robust againt corruption to the state file. Change an XXX in pareto.rs: a ticket is now open. 2021-12-08T15:29:44Z Nick Mathewson nickm@torproject.org 2021-12-08T15:29:44Z urn:sha1:8f200223f754349ed43c9b681f1f2350b8aa72fa Use a panic-free function to multiply timeouts. 2021-12-06T21:00:17Z Nick Mathewson nickm@torproject.org 2021-12-06T20:55:12Z urn:sha1:d6f628c6b75a2b3958b02b8cf1a660b95082c098 Previously we used Duration::mul_f64, which panics if its output is out-of-range. That shouldn't actually be possible for the values we're giving it, but probably it's better to just multiply in a safe way. This resolves a couple of XXXXs and therefore relates to #231. add semicolons if nothing returned 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d Fix a few typos. 2021-11-24T23:12:44Z Nick Mathewson nickm@torproject.org 2021-11-24T22:31:42Z urn:sha1:f55950ab8d86fec3c5fbe33650c4a7001f9812b3 Also fix some commonwealth spellings that had slipped in. Basic tests for readonly estimators, and estimator migration. 2021-11-03T17:58:51Z Nick Mathewson nickm@torproject.org 2021-11-02T19:54:59Z urn:sha1:cb63449aeb8f6e0de8b694c7a70ffaa7f2a84ae4 Also add a comment about a possible problem behavior in read-only estimators.