mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.02025-08-18T19:45:55Zmisc: cleanup now that `_report!` macros support fields2025-08-18T19:45:55ZSteven Engleropara@torproject.org2025-08-09T20:31:11Zurn:sha1:2de5c18fae7be30c4ab3c3fae520c81fb3ff74edSwitch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
Update code for Edition 20242025-08-07T15:28:31ZNick Mathewsonnickm@torproject.org2025-08-07T12:44:47Zurn:sha1:0453fb4be8cf618b94230812957ce1db1afe74bd
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
dirmgr: Rename circuit to tunnel2025-08-05T18:23:02ZDavid Gouletdgoulet@torproject.org2025-06-17T19:16:12Zurn:sha1:bf154319b8b7d150629c918e41e15fb7dc47edec
Signed-off-by: David Goulet <dgoulet@torproject.org>
config-path, dirmgr, general-addr: Remove unnecessary parentheses (fmt).2025-07-15T12:52:17ZGabriela Moldovangabi@torproject.org2025-07-15T12:52:17Zurn:sha1:dad9ca3f2fd2178937bf1602d50259585d987473config-path, dirmgr, general-addr: Remove unnecessary parentheses.2025-07-15T12:29:35ZGabriela Moldovangabi@torproject.org2025-07-15T12:29:35Zurn:sha1:06f7c84f82ae424c6f528d6901d8ba51920e6e09
This resolves some nightly clippy warnings.
tor-dirmgr, tor-guardmgr: Use std::slice::from_ref as suggested by clippy.2025-07-07T16:01:42ZGabriela Moldovangabi@torproject.org2025-07-07T15:59:54Zurn:sha1:29ec638ad3b966cec3083c868fd354e0ba0d3133Temporarily suppress mismatched_lifetime_syntaxes.2025-07-07T15:50:04ZGabriela Moldovangabi@torproject.org2025-07-07T15:50:04Zurn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3
See #2060.
tor-dirmgr: Removed dependency on `once_cell`2025-06-15T02:11:18ZhashcatHitman3924-hashcatHitman@gitlab.torproject.org2025-06-15T01:36:10Zurn:sha1:23715547edaeb0e80eca0217684722dacb03ff7e
- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`.
Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>
*: suppress cognitive_complexity warnings from nightly2025-05-29T14:21:17ZNick Mathewsonnickm@torproject.org2025-05-21T14:48:35Zurn:sha1:5327d3e22a83b8469a5d4191d92e1364344ddc93
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.
I have mixed feelings about these warnings: On the plus side,
they really do help to detect functions that are twistier than they
need to be. On the minus side, they get confused by tracing macros,
and the "allows" do pile up. But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.