mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.1.2

tor-dirmgr: Work around an apparent regression in `time`.

2023-02-17T19:36:19Z

Some code in our tests that worked fine with time 0.3.17 no longer works with 0.3.19, despite the semver. See https://github.com/time-rs/time/issues/552 for the upstream bug.

tor-netdoc: Change fill_from_previous_netdir

2023-02-09T12:56:18Z

* Remove the return value, which was not used anywhere. Also remove the code to calculate the return value. * Take an Arc rather than a reference. We are going to want this for HS support. This has no overall effect on the lifetime of the4 Arc, which was owned at the one call site and then imediately dropped. * Change the documentation to explain what the function's role is in the netdir API, rather than the fiddly details of what it actually does internally. Relegate the latter to a code comment. (When we have HS, this will do more, or, at least, make further arrangements.)

Use ErrorReport - run rustfmt

2023-01-30T18:52:32Z

Split off for ease of review and possible rebase.

Use ErrorReport's .report() for two errors in error! in bridgedesc.rs

2023-01-30T18:52:32Z

No functional change, just using the new idiom.

Use ErrorReport for errors in warn! in tor-dirmgr

2023-01-30T18:52:32Z

Use ErrorReport for errors in info! in tor-dirmgr

2023-01-30T18:04:57Z

"Fix" remaining unchecked-subtraction warnings.

2023-01-27T14:16:41Z

In both cases I think it's fine to panic; but it's best to do so explicitly.

Allow clippy::unchecked_duration_subtraction in tests

2023-01-27T13:28:02Z

This panics on error, and we're fine with a panic on misbehavior in tests.

Disable clippy::unlinlined-format-args

2023-01-27T13:27:47Z

This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748.

Complete our migration to base64ct.

2023-01-20T13:06:30Z

This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.