| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Soon `handle_in_order_relay_msg()` will be called from other places too,
for handling deferred out-of-order conflux messages.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is a direct translation of C Tor's `conflux_should_multiplex()`.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The leg removal reason will be shared with the initiator of the conflux
handshake (i.e. the sender of the `CtrlMsg` initiating the handshake),
if the tunnel is a multi-path tunnel with conflux handshakes in
progress.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The reactor will need to notify the conflux handshake initiator (the
sender of the `CtrlMsg` that triggered the handshake) of conflux set
readiness, so it needs to keep track of the status of the circuits it
was asked to link.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
These will be used for sending the conflux handshake outcome to the
reactor user.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We will need this to implement conflux handshake timeouts,
and to get the current time for RTT calculations.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This will be soon needed in the `ConfluxSet` implementation too.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This will be shared by all circuits in the set, and will be used during
the conflux handshake.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
It doesn't actually need to be `pub(super)`.
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
shadow CI test: only require 1 successful HS transfer
See merge request tpo/core/arti!2991
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per previous discussion there is some known flakiness around hidden
services with TestingTorNetwork enabled:
<https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1399#note_2921505>
Previously, only requiring 5 of 10 transfers to succeed has been enough
to keep this stable, but recently we've gotten unlucky and dipped under
this threshold: <https://gitlab.torproject.org/tpo/core/arti/-/issues/1986>
More investigation is warranted, especially wrt why the problem seems
to mostly be affecting articlient-onion-auth, but for now it's better to
have a low success threshold than to have folks overriding the CI
failure.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Updates to Release.md from recent release
See merge request tpo/core/arti!2987
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We don't use this branch for our website any longer.
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We should check what dependencies we cannot upgrade,
so that the release engineer has some history about where we got
stuck last time.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
TODO: Implement HasKind trait for TorAddrError
See merge request tpo/core/arti!2965
|
| | | | | | | | |
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit implements the HasKind trait for TorAddrError in address.rs,
mapping all variants to the InvalidStreamTarget error kind. It also updates
the ErrorDetail implementation in err.rs to delegate to TorAddrError's
HasKind implementation instead of hardcoding the error kind.
Resolves TODOs in address.rs and err.rs.
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enable --features=full on reproducible builds.
Closes #1964
See merge request tpo/core/arti!2956
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a workaround for
https://github.com/eira-fransham/crunchy/pull/17
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We generally recommend that people build with --features=full IRL,
so this better matches what we're hoping they come up with.
Additionally, it will help cases like #1964, where packagers would
like to use reproducible builds as inputs to their own packages.
Closes #1964
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
ci: bump shadow for EPOLLRDHUP fix
Closes #1972
See merge request tpo/core/arti!2968
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit 5f6bd6c42ea97c3f659280a32e206db77f4b4da6.
This workaround is no longer needed since the underlying bugs have been
fixed in shadow (See https://github.com/shadow/shadow/issues/3100 and
https://github.com/shadow/shadow/pull/3574), and the CI has been bumped
to use a version of shadow with these fixes.
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
Fixes #1972
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
arti-ureq: Specify versions for dependencies.
See merge request tpo/core/arti!2984
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
release: Fix CHANGELOG.md formatting.
See merge request tpo/core/arti!2983
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Oops, shouldn't have pushed the previous MR without letting CI run
fully...
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
release: Bump versions.
See merge request tpo/core/arti!2981
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
```
cargo set-version --bump patch -p arti
```
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
|
| | |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
Of these, only hashx and fs-mistrust have changed, as per:
```
./maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
```
So these were updated with:
```
./maint/bump_nodep hashx fs-mistrust
```
|
