| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This change is needed to satisfy `maint/cargo_sort`
|
| | | | | | | | |
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | | |
As per the team decision from the 14 Oct Arti sync.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
arti-relay: More work on bootstrapping
See merge request tpo/core/arti!3375
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We don't want to create new files just when creating a `InertTorRelay`.
We should only generate the keys before bootstrapping.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | |
| | | | | |
| | | | | | |
relay: Implement a first relay background task
See merge request tpo/core/arti!3363
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We have bootstrap() to prepare everything we need before starting the
relay which yields a TorRelay.
This commit then adds a run() function which starts the relay by
launching background task. At the moment, we only have one task and it
is the channel expiry one.
The relay blocks on the task handle set until one task is on error or
stops which leads to shutting down the relay.
Part of #2217
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a background task in charge of expiring closing channels and
future work is to also prune duplicate channels.
This is not used nor called at this commit, next commit will add the
task handling.
Part of #2217
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-netdoc: parse2: Minor fixes
See merge request tpo/core/arti!3376
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Since 9ce85acb3ab0d1a0b1be6ef0f10707983f4362a3
tor-netdoc: replace impl_item_argument_as_display with NormalItemArgument
this trait impl has implications for encoding as well as parsing.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In principle some other trait might be in scope.
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
subdoc intro items aren't inherently incoherent, but implementing them
is nontrivial. Let's reject them with a bespoke error instead.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Bump MSRV from 1.85.1 to 1.86
See merge request tpo/core/arti!3382
|
| | |/ / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-netdoc: blanket impl parse2 traits for Arc
See merge request tpo/core/arti!3381
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
This replaces one ad-hoc impl and will avoid having to have any more.
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
proto: Add the initial implementation of the relay reactor(s)
See merge request tpo/core/arti!3369
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The `RelayReactor` now holds the sending end of the shutdown broadcast
channel, so if `RelayReactor` exits, both the forward and the backward
relay reactor will notice and shut down too.
Similarly, if the forward or backward reactor exits, the `RelayReactor`
will notice (because it select!s between the two), and will shut down
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I used `futures::join` by mistake: the intention here is to have
`RelayReactor` exit when either one of the fwd/bwd reactors exits.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This also clarifies why we reroute cells to `BackwardReactor`.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Things will get very confusing if every reactor uses different variable
names for this, so I am renaming it back to input.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The channel provider is used to request outgoing channels from the
`ChanMgr` in response to `EXTEND`/`EXTEND2` cells, so it belongs in the
`ForwardReactor`.
(This was leftover from the old circ reactor architecture)
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is the first step towards parallelizing stream reads and
writes.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes it a bit clearer that `cell_rx` is for moving stream data
between `ForwardReactor` and `BackwardReactor`.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
The forward/backward terminology is clearer.
|
| | | | | | | |
|