mirrors/arti.git/crates/tor-guardmgr/src/pending.rs, branch arti-v1.3.2 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2 2024-08-28T14:27:46Z extract tor_async_utils::oneshot into ::oneshot-fused-workaround 2024-08-28T14:27:46Z Jim Newsome jnewsome@torproject.org 2024-08-22T19:20:36Z urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1 Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency. oneshot: Apply deferred rustfmt churn 2023-10-11T15:19:46Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-11T15:09:09Z urn:sha1:665ba4f6b6ed2de6f723177d5472e7ee1440599e cargo fmt, precisely. oneshot: Use veneer in tor-guardmgr 2023-10-11T15:19:21Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-11T14:09:26Z urn:sha1:0f189093db1e49042827ae4d09bbb4bd93e966cc Create and use API to report guard/fallback skew. 2022-04-07T14:47:45Z Nick Mathewson nickm@torproject.org 2022-04-06T13:05:35Z urn:sha1:c3c43b088e9f8dcbe876c277c3af14705244e8b0 (The information is not yet recorded.) Refactor FirstHopId into type-differentiated form 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. Rename Guard=>FirstHop, GuardId=>FirstHopId 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. Clarify documentation about GuardUsable constructors 2022-03-30T14:40:14Z Nick Mathewson nickm@torproject.org 2022-03-29T12:21:11Z urn:sha1:c721c8ee534b49e960622741307bdca6e613a403 Add a TODO about an unslightly type. 2022-03-30T14:40:14Z Nick Mathewson nickm@torproject.org 2022-03-29T12:20:53Z urn:sha1:16ce29ef59116f13e7e2aa181d05200edc1f6aff Add status tracking to FallbackDir. 2022-03-30T14:39:09Z Nick Mathewson nickm@torproject.org 2022-03-25T23:19:57Z urn:sha1:bfb2353a8f627b189e104e606b3284fdfaa6d98b We do this by creating a new FallbackSet type that includes status information, and updating the GuardMgr APIs to record success and failure about it when appropriate. We can use this to mark FallbackDirs retriable (or not). With this change, FallbackDir is now stored internally as a Guard in the GuardMgr crate. That's fine: the FallbackDir type really only matters for configuration. GuardMgr: some prep work for returning fallbacks as guards. 2022-03-30T14:39:09Z Nick Mathewson nickm@torproject.org 2022-03-25T20:49:35Z urn:sha1:a4a5f2163d7d79d152498f0a59345a22ec1d55ca We need to extend our notion of "the origin of a guard" to include "somewhere outside the guard list"; we need the ability to return a FallbackDir as a Guard; and we need to remember a few more pieces of information in each pending request. As before, this commit may break compilation; it will be restored soon.