| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
rustfmt has grown opinions about how let ... else ... ought to be
formatted. They don't always agree with our previous manual
decisions.
I think our policy is to always insist on rustfmt. When that version
of rustfmt hits stable, our CI will start to fail for everyone.
(Right now this discrepancy just causes trouble for contributors who
are using nightly by default.)
|
| | |
|
| |
|
|
|
|
|
|
| |
The effect is that everywhere a RetryError is used, the error sources
for the contained errors will be Display'd.
In tor-hsclient we no longer need to explicitly wrap things up in
tor_error::Report.
|
| |\
| |
| |
| |
| | |
clippy: Allow some of our existing code patterns
See merge request tpo/core/arti!1396
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Overhaul send_control_message
See merge request tpo/core/arti!1367
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This is just a placeholder for now, but it'll be a thing you can send
more messages with.
|
| | | |
| | |
| | |
| | | |
Was send_control_message.
|
| | | |
| | |
| | |
| | |
| | | |
We're going to let people start a conversation and either expect to
receive first, or send messages ad-hoc later.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Was UninstallHandler. We are going to talk more about conversations
and less about handlers (although, the fact of there being a handler
will still be visible).
|
| |\| |
| |/
|/|
| |
| | |
tor-hsclient: Mock traits: Work around an async boobytrap
See merge request tpo/core/arti!1365
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
See here for documentation on the lint:
https://rust-lang.github.io/rust-clippy/master/index.html#/diverging_sub_expression
The issue here, from what I can tell, is that the lint triggers
whenever you use a diverging expression as a function body within an
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I identified the cases to replace by searching for the string
`.report()`. There are a few that I didn't change:
* A couple of cases that used anyhow::Error,
* One case that reported two Errors.
* Two cases in `tor_hsclient::err` that just did
`error!("Bug: {}")`.
I have also not audited the cases in `tor-hsclient` where we're using
`tor_error::Report` manually.
Nonetheless, closes #949.
|
| | |
| |
| |
| | |
Closes #950.
|
| |/
|
|
|
|
| |
Now we can reliably wait precisely for the tasks to be all waiting.
This test case no longer involves any real executor.
|
| | |
|
| |
|
|
| |
`ArtiPathComponent` is a more generic version of `HsClientSpecifier`.
|
| |\
| |
| |
| |
| | |
tor-hsclient: Use estimated timeouts
See merge request tpo/core/arti!1342
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Replacing RPT_IPT_TIMEOUT is not entirely straightforward.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
tor-netdoc: Handle anomalous numbers of introduction points
See merge request tpo/core/arti!1332
|
| | |
| |
| |
| | |
None of the existing NetdocErrorKinds seemed right.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-hsclient: Reimplement Debug for MockCirc
See merge request tpo/core/arti!1324
|
| | | |
| | |
| | |
| | |
| | | |
This is less code. Also it now dumps the connect_called field which
was introduced in the meantime.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
tor-hsclient: Use proper CircParameters
Closes #935
See merge request tpo/core/arti!1340
|
| | | |
| | |
| | |
| | | |
Fixes #935
|
| |\| |
| | |
| | |
| | |
| | | |
tor-hsclient: Handle handshake completion error correctly
See merge request tpo/core/arti!1336
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thsi is a bit of a mouthful now, but it is comprehensible.
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1336#note_2917235
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
See
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1336#note_2917236
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We need to handle errors during the handshake. That also produces a
`tor_proto::Error` but we want to print a different message for that,
so let's rename this before adding the new variant.
|
| | |/
| |
| |
| | |
It was wrong where ti was.
|
| | |
| |
| |
| | |
Since arti!1233 this is trivial.
|
| |/
|
|
|
| |
For some reason this wasn't used in the actual errors,
although it *was* used in the types of the functions etc.
|
| |\
| |
| |
| |
| | |
tor-hsclient: Discuss intro circuit extend-and-reuse
See merge request tpo/core/arti!1298
|
| | | |
|
| | |
| |
| |
| | |
This is a summary of a discussion I had on IRC.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Conceptually this is a fixup to
HS configuration: Add retry parameters to configuration
which erroneously removed these comments - they were intended to apply
to *all* these parameters, not just the max attempts.
Not marking it as fixup! because that would involve merge conflicts.
|