mirrors/arti.git/crates/tor-guardmgr/src, branch arti-v1.3.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.22025-01-06T23:09:41Zclippy: deny `mod_module_files`2025-01-06T23:09:41ZSteven Engleropara@torproject.org2025-01-06T23:02:49Zurn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
add_warnings, *: Allow clippy::needless_lifetimes2024-12-03T14:27:26ZNick Mathewsonnickm@torproject.org2024-12-03T14:15:50Zurn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
Disable a lot of dead code warnings2024-10-17T10:25:24ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-16T14:27:16Zurn:sha1:107ad43db8b7d619f5076ab37c92dcce7a25c223
Now
cargo check --workspace --no-default-features --all-targets
cargo build -p arti --no-default-features --features=memquota,tokio,native-tls
are both clean.
Upgrade to derive_more version 1.0.02024-09-25T14:37:18ZNick Mathewsonnickm@torproject.org2024-09-25T14:37:18Zurn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
tor-guardmgr: Convert a TODO into a NOTE.2024-09-10T14:26:02ZGabriela Moldovangabi@torproject.org2024-09-10T14:24:15Zurn:sha1:1d71d47171b886e66eb21422fff2dcd6840f0d92
This behavior is OK, so this doesn't need to be a TODO.
See the discussion at
https://gitlab.torproject.org/tpo/core/arti/-/issues/1352#note_3015217
Closes #1352
tor-netdir: Allow access to the `ConsensusBuilder` when building test netdirs.2024-09-09T17:26:37ZGabriela Moldovangabi@torproject.org2024-09-05T15:42:08Zurn:sha1:b2b75302ab095bccdc7ccecb627e4648a3ae9419
This allows us to set SRVs for example (needed because by default, the
test `NetDir` is built from a consensus that doesn't contain any SRVs).
Fix typos2024-09-03T08:09:02ZDimitris Apostoloudimitris.apostolou@icloud.com2024-09-03T08:09:02Zurn:sha1:676f913463b7d84f34dd6101b99d03ef79cf57adextract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn: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.
tor-guardmgr: Make some vanguard test helpers public (fmt).2024-06-20T12:12:55ZGabriela Moldovangabi@torproject.org2024-06-12T11:13:10Zurn:sha1:0eb28a066f8859c8ff3e35b7a8dba5460e200433tor-guardmgr: Make some vanguard test helpers public.2024-06-20T12:12:55ZGabriela Moldovangabi@torproject.org2024-06-10T12:35:23Zurn:sha1:df366496b8204ca2435ee264499bc5c1ebfacad8
We will soon need these helpers outside of `tor-guardmgr` too.
This commit is mainly code motion.