| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The "full" feature is a catch-all for all features, _except_:
* Those that select a particular implementation (like
tor-llcrypto/with-openssl) or build flag (like "static")
* Those that are experimental or unstable (like "experimental-api")
* Those that are testing-only.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Fix several clippy issues, most with nightly
See merge request tpo/core/arti!588
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Without this, clippy is error-free, but `cargo test` somehow gives a
warning.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There is not, apparently, an eprintln equivalent for
allow-dbg-in-tests.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is apparently a new warning from clippy nightly, documented in
https://rust-lang.github.io/rust-clippy/master/index.html#significant_drop_in_scrutinee .
I'm not in love with the temporary variables that this warning wants
me to introduce, but it does seem like a decent way to avoid some
kinds of deadlock.
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-netdir: testnet: Make construct_netdir infallible
See merge request tpo/core/arti!585
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Run rustfmt. Separate commit to make review of the substantive commit
easier.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is a *lot* of unwraps. The function takes no parameters and
is used only for testing. It ought to be infallible.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use TaskSchedule to sleep in directory bootstrapping
Closes #497
See merge request tpo/core/arti!571
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will allow somebody else to call bootstrap() if bootstrap() fails
the first time.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change also means that we need to create the handle and scheduler
earlier in the process of creating the DirMgr. If we don't, we won't
have a way to manage the task before bootstrap() returns.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change (not yet exposed as an API) will let the TorClient have
a `TaskHandle` corresponding to the directory task, letting it
make the directory task dormant as needed.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Having this alias makes it easier to implement more complex
schedules, like those used in DirMgr.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Unlike "cancel" and "fire", "suspend" and "resume" don't change any
pending timers or events: they just prevent execution of those
events for a while, and let them resume later on.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
config: Be consistent about Option
Closes #488
See merge request tpo/core/arti!582
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per point 3 in
https://gitlab.torproject.org/tpo/core/arti/-/issues/488
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per point 1 in
https://gitlab.torproject.org/tpo/core/arti/-/issues/488
|
| |\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | | |
tor-error: Fix a broken intra-doc link
See merge request tpo/core/arti!580
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
I didn't spot this in review amongst the other messages from Nightly.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tor-bytes: read_nested_*: Take a closure
Closes #498
See merge request tpo/core/arti!579
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I disagree with almost all of these layout decisions...
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This eliminates the possibility of writing the bug of failing to call
`should_be_exhausted`.
As per this discussion
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/572#note_2811464
Fixes #498
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Have channel reactor able to send channel padding
See merge request tpo/core/arti!574
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
There aren't very many.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Replace four very similar "ids in request"
See merge request tpo/core/arti!577
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In reviewing !553 I noticed that the empty digest list error had to be
handled in two places. I filed #492 about the duplication.
In fact it turns out to have been quadruplication.
The new code also avoids cloning the underlying objects, instead
sorting a Vec of references.
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
I'm not sure this is right. But providing a test case for it before
my next change ensures that my refactoring doesn't change the
behaviour.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix typos
See merge request tpo/core/arti!578
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Introduce and use nested length reader/writers
See merge request tpo/core/arti!572
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This does away entirely with `wire_addr_len`, which recapitulates the
length calculation.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We'll want this in a moment.
|
| |/ / / /
| | | |
| | | |
| | | | |
Writing is going to be able to give errors too.
|