mirrors/arti.git/crates/tor-keymgr/src, branch arti-v1.6.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.02025-09-29T19:30:03ZRemove "doc_auto_cfg" incantation from all crates.2025-09-29T19:30:03ZNick Mathewsonnickm@torproject.org2025-09-29T18:30:14Zurn:sha1:808b0ec2e3735a6dbbebeb857a3d6040ae02c697
This feature has been removed from nightly, in favor of doc_cfg.
tor-keymgr: Fix `KeyMgr::list_keystores` description2025-09-22T08:30:56Zhjrgrn3874-hjrgrn@gitlab.torproject.org2025-09-22T08:30:56Zurn:sha1:6fa435edccd0d5bfab41108f3b2b455a5c7652f5arti: keys: Add `keys check-integrity` CLI tool2025-09-04T12:14:22Zhjrgrn3874-hjrgrn@gitlab.torproject.org2025-08-09T10:58:03Zurn:sha1:9bca678d898f1f0be8b2ff69adf3444998322ef6misc: cleanup now that `_report!` macros support fields2025-08-18T19:45:55ZSteven Engleropara@torproject.org2025-08-09T20:31:11Zurn:sha1:2de5c18fae7be30c4ab3c3fae520c81fb3ff74edclippy: fix `clippy::implicit_clone` errors2025-08-11T15:18:41ZSteven Engleropara@torproject.org2025-08-11T15:18:16Zurn:sha1:691177eae9f0d3117220f7927237fbf9fafc79e6
```text
error: implicitly cloning a `String` by calling `to_string` on its dereferenced type
--> crates/tor-config/src/lib.rs:109:32
|
109 | V::String(_, s) => s.to_string(),
| ^^^^^^^^^^^^^ help: consider using: `s.clone()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#implicit_clone
note: the lint level is defined here
--> crates/tor-config/src/lib.rs:20:9
|
20 | #![deny(clippy::implicit_clone)]
| ^^^^^^^^^^^^^^^^^^^^^^
```
Fix warnings and errors from edition 2024.2025-08-07T15:28:39ZNick Mathewsonnickm@torproject.org2025-08-06T01:54:12Zurn:sha1:4fbbffe7c14b2df6290268b6e3c8530106ab2529
The two main causes of errors were:
- Since some of the lifetime rules have changed, we no longer need
to do as many "bind a variable and immediately return it"
patterns, and so clippy now warns about them.
- We needed to adjust the explicit captures (`use<...>`)
in a couple of our RPIT instances.
Switch 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.
Fix errors from rustdoc nightly.2025-08-05T13:34:23ZNick Mathewsonnickm@torproject.org2025-08-05T13:34:23Zurn:sha1:30a36b17593c10255ddd37eb7579c895c6629b67Use new DisplayRedacted/DebugRedacted code for HsId.2025-07-31T13:49:51ZNick Mathewsonnickm@torproject.org2025-07-29T18:49:37Zurn:sha1:24b56a134a0542965fd4bb76f39300523fde0213
Closes #2012.