mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.3.0 2022-04-25T17:06:26Z 2022-04-25T17:06:26Z Nick Mathewson nickm@torproject.org 2022-04-25T16:40:33Z urn:sha1:2f6bc6bdc431fa36de70a167eea777dcf3f60bf2 Remove all `use` statements for `TryFrom` and `TryInto`. These are now redundant in Rust 2021. 2022-04-24T22:27:29Z trinity-1686a trinity@deuxfleurs.fr 2022-04-24T22:27:29Z urn:sha1:b9dd23de91bba8866052579b1d974691201cb075 2022-04-13T12:51:23Z eta tor@eta.st 2022-04-13T12:51:23Z urn:sha1:41dd682552ff9a8f8c0f766da589773d16257d2a Report skew estimates from arti-client See merge request tpo/core/arti!455 2022-04-12T13:19:10Z Nick Mathewson nickm@torproject.org 2022-04-12T13:19:10Z urn:sha1:4582dddca8d5f301d6d68203c7309f292a68d8b5 Rather than running preemptive circuit construction every 10 seconds, we change it to back off when it is "failing". (We define "failing" as creating no new circuits, and as giving at least one error.) This change means that we'll have one less reason to hammer the network when our connectivity is failed for some reason. Closes #437. Part of #329. 2022-04-12T13:04:10Z Nick Mathewson nickm@torproject.org 2022-04-12T13:04:10Z urn:sha1:482c022e23884ae53a00eadb46a7950ba0f8bc71 Now that we have TaskSchedule, we don't need to expose these any longer. 2022-04-12T12:41:32Z Nick Mathewson nickm@torproject.org 2022-04-12T12:41:32Z urn:sha1:3d5276a9cc6030751f9b4ff541c4055a4e66f75c This feature is similar to ChanProvenance from ChanMgr, except that we don't yet need to report it outside the crate. I'm going to use it to distinguish newly created circuits from existing circuits in the preemptive circuit builder. 2022-04-12T12:03:49Z Nick Mathewson nickm@torproject.org 2022-04-11T19:18:59Z urn:sha1:72f00daf121ca0bce965097e7f187ec4dbfdf1c3 2022-03-30T14:41:57Z Nick Mathewson nickm@torproject.org 2022-03-30T14:41:57Z urn:sha1:2bb3ba7886571153a46dc6d5de4a6e6876863957 2022-03-30T14:41:39Z Nick Mathewson nickm@torproject.org 2022-03-29T14:55:20Z urn:sha1:6282df34fb00c3b8b686553e05f8d3172b017ed0 The FirstHopId type now records an enum that stores whether the hop is a guard or a fallback. This change addresses concerns about remembering to check the type or source of an Id before passing it down to the FallbackState or GuardSet. Making this change required an API change, so that dirmgr can report success/failure status without actually knowing whether it's using a fallback or a guard. 2022-03-30T14:40:59Z Nick Mathewson nickm@torproject.org 2022-03-29T13:05:39Z urn:sha1:13af6134f6180f7241daca9206fa49ed5f26829d This is preparation for having separate GuardId and FirstHopId types that distinguish which back-end they index.