| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per our policy, every one of these gets a minor bump.
Generated with:
```
for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do
cargo set-version --bump minor -p $crate;
done
```
(Note the use of `-` at the end end of the grep pattern to prevent
matching the `arti` crate.)
|
| |\
| |
| |
| |
| | |
Upgrade MSRV to 1.77 , and rusqlite to 0.32.1
See merge request tpo/core/arti!2451
|
| | |
| |
| |
| | |
This will allow us to upgrade to the latest version of rusqlite.
|
| |/
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
memquota: be more firm about avoiding panics, and tidy up docs
See merge request tpo/core/arti!2404
|
| | | |
|
| | |
| |
| |
| | |
Remove extraneous text, wrap it, and change to a more declarative style.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This detect possibly-panicking operations.
Empirically this lint seems rather better now.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
It is not locally obvious that n_particips can't be zero, here.
Certainly if it *is* that would be state corruption, but I don't think
I can quite rule it out in the presence of a bug somewhere else.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
In these two places, underflow is statically impossible, but
demonstrating that to the compiler is probably too onerous.
|
| | |
| |
| |
| |
| | |
This sentence is very important piece of overall explanation, but
didn't make it into the crate level docs.
|
| |/ |
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2374#note_3070500
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
We're about to change the config behaviour; adding these tests first
allows us to demonstrate the changes.
|
| |
|
|
|
|
|
|
|
|
| |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.22.0
done
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
|
|
| |
This makes more sense than having them alphabetical.
Noticed while I was working on moving other code.
|
| |\
| |
| |
| |
| | |
Add and use `PeekableStream` and `UnobtrusivePeekableStream`
See merge request tpo/core/arti!2345
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Reported at
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2351#note_3062292
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This will hopefully allow much caller code to be compiled out.
The users (IsParticipant impls) don't generally need to bother with
it - they can just ignore it.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Now if we run doctests without the feature enabled, we test that a
no-op MemoryQuotaTracker works.
Those tests aren't currently run in CI, but they will be after !2350.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Wrap up most of the structures in IfEnabled.
Sadly this diff is very noisy. I experimented with macros for the
little enabled check at the start of each function but they didn't
really help.
We don't test this yet. We'll do a smoke test of this later.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We're going to bind self_ to something more complicated, in each of
these functions, and that's what all these field references etc. will
need to refer to.
Do this mechanical change first for clarity.
|