mirrors/arti.git/crates/tor-guardmgr/src/lib.rs, branch arti-v1.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.02025-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.
extract 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-config: Apply deferred cargo fmt.2024-06-03T09:47:32ZGabriela Moldovangabi@torproject.org2024-05-16T16:34:48Zurn:sha1:1128338f90abd74016b65c3a12cb4283324a17cbtor-config: Add macro for implementing NotAutoValue.2024-06-03T09:47:32ZGabriela Moldovangabi@torproject.org2024-05-16T13:37:45Zurn:sha1:f5146d0909bd50c05f435aff271031d150ac61c8tor-config: Add NotAutoValue trait bound to ExplicitOrAuto inner type.2024-06-03T09:47:32ZGabriela Moldovangabi@torproject.org2024-05-16T13:31:19Zurn:sha1:2ebcde2309ffb358c42a5a094e261e900bda0537
This is a safeguard to prevent users from using ExplicitOrAuto with
types that serialize to the same value as ExplicitOrAuto::Auto.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2146#note_3030692
tor-guardmgr: Replace From impl with VanguardConfig::mode accessor.2024-06-03T09:47:32ZGabriela Moldovangabi@torproject.org2024-05-16T13:15:56Zurn:sha1:d64f62abe379e673591d20b36dfbb638aa5f263dtor-guardmgr: Use ExplicitOrAuto in the VanguardConfig2024-06-03T09:47:32ZGabriela Moldovangabi@torproject.org2024-05-13T13:43:52Zurn:sha1:d434d3266ceadfa1446f20e6f9f26d9c585b9c42