| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
This fixes a warning from nightly clippy.
|
| |
|
|
| |
Closes #839
|
| |
|
|
| |
Closes #803, I hope.
|
| |
|
|
|
|
|
| |
My goal here is to make sure that we can't confuse
one download operation and another, and that we actually know
what's going on. Previously, not all state transitions or
attempts to fetch information actually corresponded to a log.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
DirMgr: Detect that directory state is ready if it begins with all MDs
Closes #802
See merge request tpo/core/arti!1126
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, we'd only call PendingNetDir::upgrade_if_necesessary
when adding a microdescriptor. But if it began already having all
of its descriptors (because we found them in the cache), we wouldn't
actually upgrade it to a PendingNetDir::Yielding, which would make
it unusable, and would make us schedule its reset time too far
in the future.
Fixes #802.
|
| | | |
|
| |/
|
|
|
|
| |
Now that we require a version of Rust that allows
`b.then_some(v)`, clippy complains about our use of
`b.then(|| v)`.
|
| | |
|
| |
|
|
|
| |
Apparently 1.68 now warns when you call into_iter() on something
that's already an iterator. Fair enough. Let's stop doing that.
|
| |
|
|
|
|
|
|
|
|
|
| |
Doing this means that any attempt to use a read-only store would
crash as soon as it found that the consensus was usable.
It seems that this bug was introduced at some point doing all the
dirmgr refactors we did over the past year. Perhaps there should be
a test for running with a read-only store.
Fixes #779
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove the return value, which was not used anywhere.
Also remove the code to calculate the return value.
* Take an Arc<NetDir> 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.)
|
| |
|
|
| |
Split off for ease of review and possible rebase.
|
| |
|
|
| |
No functional change, just using the new idiom.
|
| | |
|
| | |
|
| |
|
|
|
| |
In both cases I think it's fine to panic; but it's best to do so
explicitly.
|
| |
|
|
|
| |
This panics on error, and we're fine with a panic on misbehavior in
tests.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This is precisely the result of running the rune in
maint/adhoc-add-lint-blocks.
|
| |
|
|
|
|
|
| |
This is the hunks from running the rune in maint/adhoc-add-lint-blocks
but which require some subsequent manual fixup: usually, deleting
now-superfluous outer allows, but in some cases manually putting back
lints that the adhoc script deleted.
|
| |\
| |
| |
| |
| | |
A few spelling fixes for bridgedescmgr code
See merge request tpo/core/arti!925
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
dirauth: Remove Faravahar
See merge request tpo/core/arti!924
|
| | |/
| |
| |
| |
| |
| | |
See https://gitlab.torproject.org/tpo/core/tor/-/issues/40688
Signed-off-by: David Goulet <[email protected]>
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
We are rotating moria1's key due to a break-in few weeks ago. See
https://gitlab.torproject.org/tpo/core/tor/-/issues/40722 for more
details.
The original MR for C-tor (tor.git) done by Roger Dingledine, moria1's
operator, is here:
https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/662
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/861#note_2856922
|
| | |
|
| |
|
|
| |
Fixes #630
|
| | |
|
| | |
|
| |
|
|
| |
BridgeConfig is itself an Arc now, so these are redundant.
|
| |
|
|
| |
These slipped in while nightly was broken.
|
| |
|
|
|
| |
It looks like, despite a few false starts, they've got this warning
right; there weren't any false positives.
|
| |
|
|
|
|
|
| |
Now the Store is constructed by arti_client, solving the problem
described here
https://gitlab.torproject.org/tpo/core/arti/-/issues/631#note_2853665
but in a different way.
|
| |
|
|
| |
rustfmt only, broken out to ease review.
|
| |
|
|
| |
We are going to change DirMgr's constructors to also take a DirMgrStore.
|
| | |
|
| |
|
|
| |
This will allow us to get rid of a needless trait impl.
|
| |
|
|
|
|
|
|
| |
This seems tidier to me.
(It saved a lot of typing when I was trying to make some complicated
pub supertrait with sealed private supertrait, but apparently not
now.)
|
| |
|
|
| |
But right now, don't do anything with it. That will come in a future MR.
|
| | |
|
| |
|
|
| |
This is part of #630.
|
| |\
| |
| |
| |
| | |
Use ErrorKind::TorAccessFailed for misbehaving bridges
See merge request tpo/core/arti!842
|
| | |
| |
| |
| | |
(Use semantic linefeed for the doc comment.)
|
| |\ \
| | |
| | |
| | |
| | | |
bridge descs: Add tests for process_document
See merge request tpo/core/arti!841
|
| | |/ |
|