| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is needed because we want to reuse `StreamTarget` and `DataStream`
on the relay side too, but to do that, we need to abstract away the
tunnel/circuit type (prior to this MR, `StreamTarget` was was
client-specific, as it used to wrap a client tunnel).
Note that `StreamTarget` needs a handle to the client/relay circuit
reactor because it needs to be able to shut down the circuit if a
protocol error occurs (cells carrying stream data are parsed late,
*outside* of the reactor, so if e.g. a cell fails to parse, the
`DataReaderImpl` needs to be able to shut it down), and because it needs
to be able to inform the reactor of flow control-related events (such as
drain rate update).
|
| | | | | |
| | | | |
| | | | |
| | | | | |
For relays, the hop of the StreamTarget will be set to `None`.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I've made `run()` more similar to its client circuit reactor counterpart
(I think the error reporting will be better, and if we ever need to make
the reactor public, it will be easier this way because now `run()`
doesn't expose the crate-private `ReactorError` type).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is already namespaced under the `relay` module so the `Relay`
prefix is redundant.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This will be needed soon.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We are about to use `StreamReqInfo` for exit streams too.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This MPSC channel now has zero buffering, because if the backward
reactor can't send the cell, the forward reactor must immediately stop
reading from its inputs (note that the backward reactor's Tor channel
towards the client *does* have a buffering layer).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There are other types of messages (like circuit-level SENDMEs) that need
to be handled in the backward reactor too.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We will soon need a handle to the runtime in BackwardReactor (we need a
time provider to call `note_sendme_received()`).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We need to avoid reading from all of these if the chan_sender isn't
ready, because otherwise we can't provide backpressure.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The backward reactor needs this for handling padding (because it may
need to e.g. put the chan sender in a blocked state).
Note that `CircuitCellSender` has an underlying
`SometimesUnboundedSink`, so from now on we must be very careful and
avoid writing to the `chan_sender` if it's not ready (because otherwise
we can end up buffering unboundedly). The next commit will add some
extra checks against reading from futures::Streams that might cause us
to write to the `chan_sender` sink (futures::Sink).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rewriting the code this way reduces the indentation level for the
"recognized cell" case (which is not yet implemented, but will be very
soon), thereby making it more readable.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: Rework ItemValueParseable, netdoc(rest, with)
See merge request tpo/core/arti!3502
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3502/diffs?commit_id=f9a6d90ec6d5abf2958534d2c100c84f325e3634#2525aaf11b44162850101813478c4734160e11fa_920_919
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The error is not really discarded (which would seem to mean ignoring
it). The erorr *value* is discarded and is replaced with a less
informative error value.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The path in `with` must always be a module, not a function, because we
need to use it for encoding too.
In the case of `rest`, it's probably sensible to require a different
function name, given that the semantics are subtly different to those
of `rest` without `with`, since the latter can only get a single word
but with `rest` you get the whole line.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
Added `staticlib` crate-type to arti-rpc-client-core which is needed for iOS.
See merge request tpo/core/arti!3523
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove semver.md files post-release
See merge request tpo/core/arti!3520
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
release: Bump metrics-exporter-prometheus
See merge request tpo/core/arti!3521
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
See #2281
This reverts commit c00d381068cd8b88d6b12d8c7be8d4e1dafc828d.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
They've bumped their MSRV to 1.86 in this release, but that is okay,
because we are also on 1.86.
See the [criterion changelog] for more details.
[criterion changelog]: https://github.com/criterion-rs/criterion.rs/blob/master/CHANGELOG.md#080---2025-11-29
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Part of #2278
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
Part of #2278
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tor-config: Refactor `Listen` to make usable for arti-relay
See merge request tpo/core/arti!3469
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Assumes that 0.37.0 will be the next version number.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
There was no reason for this to be public.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This does a little extra cloning, but I think is easier to read.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
For example the old message would look like:
```text
target/debug/arti: error: read configuration: Config contents not as
expected: Couldn't load configuration: data did not match any variant of
untagged enum ListenSerde for key "default.proxy.socks_listen" in
command line
```
The new message looks like:
```text
target/debug/arti: error: read configuration: Config contents not as
expected: Couldn't load configuration: value was not a bool, `u16`
integer, string, or list of integers/strings for key
"default.proxy.socks_listen" in command line
```
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | |
| | | | | | |
| | | | | | | |
shadow CI: tweak HS required success thresholds
See merge request tpo/core/arti!3515
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
None of the failures currently recorded in
https://gitlab.torproject.org/tpo/core/arti/-/issues/2209 involve the
c-tor client. I think we can safely require all xfers to succeed for the
c-tor client.
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
From 9/10 to 5/10.
This is to mitigate flakiness.
See
https://gitlab.torproject.org/tpo/core/arti/-/issues/2209#note_3295789
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
ci: Disable echoing in shadow test script.
See merge request tpo/core/arti!3496
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Having this all on one line makes it easier to read.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Now that we no longer echo these, this is useful.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Now that we no longer echo this, it's potentially useful to have it.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I find that the echoing here does not really contribute to my
understanding of what's going on, and it makes the output quite
difficult to parse.
|