mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.4.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.12025-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.
TimerangeBound: Stop using std::ops::Bound.2024-11-25T18:20:11ZWesley Aptekar-Casselsme@wesleyac.com2024-10-15T13:58:29Zurn:sha1:1659495eb30ae6a17058418b6d00592373cfdf65
Fixes: #1691
tor-dirmgr: don't support changing `DirMgrConfig::cache_trust`2024-11-06T01:16:07ZSteven Engleropara@torproject.org2024-11-05T22:24:51Zurn:sha1:04ffb50829cbfb484d3427dcfae8f3cd720f5afa
`DirMgrConfig::update_from_config` uses the old value and not the new
value, so it should be reported using `Reconfigure::cannot_change`.
Replace _ => panic!() elsewhere2024-10-15T11:14:10ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-15T11:14:10Zurn:sha1:0f6eadfd9836b3507ad22a0bf4fae5749b8cf8b8Upgrade 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.
rtcompat: Add an extension trait for building modified Runtimes2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-18T20:43:50Zurn:sha1:0121822457f77b9d669c38194919b5bfd908b9a1
With this extension trait, we no longer need to construct
`CompoundRuntime` directly outside of tor-rtcompat. This in turn
will make it a little less painful when we have to add more generics
to CompoundRuntime.
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.
Merge branch 'sqlite-race' into 'main'2024-07-31T08:59:43Zgabi-250gabi@torproject.org2024-07-31T08:59:43Zurn:sha1:041ef9b3068d281bbcdd32f65b57215f835dbb42
tor-dirmgr: Return an error if storage is readonly and DB is missing/incompatbile.
Closes #1497
See merge request tpo/core/arti!2283