| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Additionally, document that this tool requires particular versions
of nightly, since the rustdoc json format is unstable.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
linkspec: Fix nightly warning about elided lifetime
See merge request tpo/core/arti!2575
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This warning shows up when running `cargo +nightly doc`.
Apparently nightly doesn't like it when we have elided a lifetime
that has a perfectly good name.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Compile in memquota feature by default
See merge request tpo/core/arti!2569
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Mark it no longer experimental, but part of full. And document it.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Mark it no longer experimental, but part of full. And document it.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
And document the Cargo features.
This compiles in the memquota support for people who depend directly
on tor-memquota. But all our in-tree dependencies turn off default
features, so this doesn't have any effect for in-tree crates.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Sort them alphabetically.
Use the bullet point style we see elsewhere.
Use the same headings as elsewhere.
|
| | | | | | |
|
| |\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allow arti cfg.rs test cases to more precisely control cargo features
See merge request tpo/core/arti!2561
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2561#note_3097443
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2561#note_3097442
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As suggested
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2561#note_3097441
I don't think we can have += since it may not be bash.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Work around awkward cargo behaviour and allow us to more reliably test
disabled features, even if they're enabled by default at lower levels.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This is very useful when iterating through CI.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This new feature lets us provide the "enable these options which are
needed to make the tests pass" featrure, which is different for each
of the afflicted crates. Then we can test these crates
tor-hsservice
arti
arti-client
which minimal features.
This will be important in a moment, as we're going to want to be
relying on actually minimal features tests in arti cfg.rs.
|
| | |/ / / |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
RPC cookie authentication spec sketch.
See merge request tpo/core/arti!2440
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
In particular, specify which methods are invoked on which objects.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Also, rename values to S_MAC and C_MAC, and include SADDR_CANONICAL
in messages.
|
| | | | | |
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
Part of #1521.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
memquota: Fix account lifetime bugs, and arrange to test mq in shadow
See merge request tpo/core/arti!2560
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Promote the associated comments.
As suggested here:
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2560#note_3097188
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2560#note_3097189
|
| | | | |
| | | |
| | | |
| | | | |
This detected the account lifetime bugs fixed in this branch.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These errors aren't necessarily memory pressure. They can occur due
to bugs, and during teardown.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This detects the bugs I have just fixed - in Shadow tests with the
feature enabled and a (large) limit set.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The DataStream is sometimes disassembled, eg by split. When that
happens, the StreamAccount would be dropped - and that was the only
strong reference.
Put a StreamAccount in each of the pieces, instead of just in the
combined DataStream struct.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We need the mq account for the stream not to collapse. The
ResolveStream object needs to contain a strong reference to it.
Have begin_stream_impl return the StreamAccount, rather than taking it
as a parameter. That makes this bug a little more obvious. It also
centralises the StreamAccount creation.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that it doesn't call CircuitAccount::new() it has no error paths,
and clippy demands we remove the Result, so it must once again become
infallible.
|