| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
This will help resolve some dependencies in our graph.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
|
| |
|
|
|
| |
Note that this contains a breaking change to the `ConfigBuilder`. This
should not break any existing toml configuration files.
|
| |\
| |
| |
| |
| | |
memquota: Fix account lifetime bugs, and arrange to test mq in shadow
See merge request tpo/core/arti!2560
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Use clippy to prevent non-mq use of mpsc::channel
Closes #1659
See merge request tpo/core/arti!2536
|
| | |
| |
| |
| |
| | |
These are the call sites where using this fucntion is correct.
(Outside tor-rtmock, which we'll do separately.)
|
| |/
|
|
| |
Fixes a TODO.
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2459#note_3086837
|
| | |
|
| |
|
|
| |
Plumbing.
|
| |
|
|
|
|
|
|
|
|
| |
Use tor_rtcompat::DynTimeProvider instead.
Ultimately, we're going to want one of these in Channel etc. The
CoarseTimeProvider generic argument then becomes pervasive.
Instead, erase it. This will involve an indirect function call each
time an item is inserted. I think that can't be helped.
|
| |
|
|
|
|
| |
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
|
| | |
|
| |
|
|
| |
I realised a way this could happen without there being a bug.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow a `Config` to represent "this is supposed to be disabled".
This involves wrapping the actual built configuration in an IfEnabled.
We treat max = usize::MAX, or max being unspecified, as "disable".
We can now reporting an error during config building if max is set but
we're compiling the feature out. Conversely, we can now make
`MemoryQuotaTracker::new()` unconditional, since enabled
confiogurations are uninhabited when the feature is compiled out.
We change how we derive the setters, deriving them from the Builder.
I chose to abolish the use of derive_builder. See the new comment on
ConfigBuilder.
|
| | |
|
| | |
|
| |
|
|
| |
Code motion of byte_qty.rs, and minimal necessary supporting changes.
|
| |
|
|
|
|
|
| |
We're going to make this into a proper public type.
It's going to move into a different crate, where there's no prelude,
so give it a bespoke set of imports too.
|
| |
|
|
|
|
|
| |
Code motion, part 1.
Also explain in comments at the top of the new module why we are doing
this at all rather than using an existing thing.
|
| |
|
|
| |
EnabledToken is pub because it's going to appear in public APIs.
|
| |
|
|
|
| |
Discussed here
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2292#note_3059928
|
| | |
|
| |
|
|
| |
We'll use this in a moment.
|
| |
|
|
|
|
| |
I'm not particularly pleased with this name. We need names for both
the type, and the trait we'll almost certainly want to introduce in
the future.
|
| | |
|
| |
|