| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This took a little refactoring, since derive_more::Foo
no longer re-exports std::ops::Foo.
|
| | | |_|/
| |/| | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Client implementation for happy families
Closes #1848
See merge request tpo/core/arti!2792
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This implements the client side of proposal 321.
It's a breaking change in netdir, since in_same_family now takes an
extra argument.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we're trying to exclude relays by family,
we need to know which lists to look at.
This information ultimately comes from the network parameters.
We could avoid this change if we just told clients
"look at all family information all the time",
but that's not what the proposal says.
This is a breaking change.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will affect some details of path selection as we provide more
info about families.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This corresponds to the entries in "family-ids" in the happy
families design.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
tor-rtmock: Provide a facility for handling other threads
See merge request tpo/core/arti!2793
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This makes it clearer that this is a specific term, which a
definition.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2793#note_3161972
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The rustdocs for a fn in a trait impl are rendered, but are very
unobvious. Put the information in the top-level documentation.
|
| | | | |
| | | |
| | | |
| | | | |
We'll expose this with some new traits in tor_rtmock.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No change to output, but much less open-coding.
Move the doc comment that was on the Debugg impl, to the `DebugTasks`
helper struct.
|
| | | | |
| | | |
| | | |
| | | | |
Show where each test sub-case is started, in stderr output.
|
| | | | |
| | | |
| | | |
| | | | |
We're going to add another call site.
|
| | | | |
| | | |
| | | |
| | | | |
We're going to add another call site.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We're going to want to add a field inside the Arc but not inside the
Mutex, so make the Arc contents into a named-fields struct.
We don't need ArcMutexData any more. Arc<Shared> will do fine.
Previously, we needed to implement .lock() on ArcMutexData but because
Arc<Shared> derefs to Shared, we can implement it on Shared just as
well.
The field in MockExecutor ought to be renamed, but that's textually
intrusive so will come in the next commit.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
In an earlier version of this code there was a Polling state, but
there isn't now.
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
This fixes an "operator precedence can trip the unwary" warning that
showed up after I updated my toolchain to 1.85.
|
| | | |
| | |
| | |
| | | |
This fixes a warning that triggers on the latest stable release (1.85).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Move StreamTarget to the tunnel module and the circuit module.
From now on streams will be implemented on tunnels, not circuits.
This moves `StreamTarget` to the tunnel module. A future change will
replace `ClientCirc` with `ClientTunnel` inside `StreamTarget`.
This is mostly code motion, best reviewed with `--color-moved`.
Signed-off-by: David Goulet <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're about to need this in `tor_proto::tunnel` which is from the
Conflux work.
In the spirit of upstreaming as much as possible, it is done now.
|
| | | |
| | |
| | |
| | |
| | | |
We will eventually need to expose this in `tor-proto`'s public API, so
it'll need to be an opaque type.
|
| | | |
| | |
| | |
| | |
| | | |
This will soon be used by the reactor-internal `ConfluxSet` as a unique
identifier for the circuit legs stored in its `SlotMap`.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds support for encoding and decoding `RELAY_CONFLUX_LINK`,
`RELAY_CONFLUX_LINKED`, and `RELAY_CONFLUX_SWITCH` cells.
Closes #1852
|
| | | |
| | |
| | |
| | | |
Part of #1852
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-proto: Move CreateHandshakeWrap to reactor module.
See merge request tpo/core/arti!2796
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This moves the `CreateHandshakeWrap` and its implementors to
`reactor::create` (none of these are used outside of the reactor).
|
| |/ / / |
|
| |/ /
| |
| |
| |
| | |
Reducing `ClientCirc` proliferation will make our lives easier when
implementing !2790.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Right now this will give us `${Xmeta as ... default ...}`, which may
improve things in the future.
The Cargo.toml syntax is precisely that from
https://docs.rs/derive-deftly/1.0.0/derive_deftly/doc_changelog/index.html#t:beta
|
| |/
|
|
|
|
|
|
|
| |
This is released now. Prepared with:
cargo upgrade -i -p derive-deftly
There is some new duplication now I think mostly because pwd-grp uses
old derive-deftly.
|
| |\
| |
| |
| |
| |
| |
| | |
arti: Upgrade 'hickory-proto' to 0.24.3
Closes #1847
See merge request tpo/core/arti!2784
|
| | |
| |
| |
| | |
This resolves RUSTSEC-2025-0006, which arti is not affected by.
|