| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-rtcompat: Remove rustls dependency in favor of futures-rustls
See merge request tpo/core/arti!2943
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
futures-rustls provides and re-exports rustls and thus the rustls
dependency is redundant.
Additionally, this removes `aws-lc-rs` and its inherent dependencies
from `Cargo.lock` and the entire project since they've been included
because the rustls dependency did not use `default-features = false`
and rustls by default now depends on `aws-lc-rs` as its crypto engine.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
NetDir::pick_n_relays: avoid some unwarranted warnings
See merge request tpo/core/arti!3028
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously we logged a warning whenever `choose_multiple_weighted`
returns `Ok(iter)`, whenever `iter` contains fewer relays than
requested.
However, this is expected behavior of `choose_multiple_weighted` if the
filtered list of relays doesn't have the requested number of relays, in
which case it should return all of the relays in the filtered list.
In particular, this condition occurs regularly in test networks when
looking for candidate relays to add to the potential guard set while
excluding those already in the potential guard set.
We still warn if the returned list is fewer than requested, *and* fewer
than available in the filtered list.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Previously it did not behave correctly when `bucket.max()` was 0 (it
would sleep for 0 time instead of infinitely, triggering a debug
assertion).
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
The token bucket is now refilled before changing the rate.
|
| | |/
|/| |
|
| |\ \
| |/
|/|
| |
| | |
expose socks proxy some more
See merge request tpo/core/arti!3016
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
The user now sets a constant amount of bytes to wait for.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Unfortunately the git diff thinks I moved the struct, but I really only
moved the comment.
|
| | |
| |
| |
| |
| | |
`DataWriter` -> `DataWriterInner`
`DataWriterNew` -> `DataWriter`
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
release: Bump versions to prepare for Arti 1.4.4.
See merge request tpo/core/arti!3024
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Done using:
cd crates/hashx/bench && cargo update
cd crates/equix/bench && cargo update
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This was done using:
cargo set-version --bump patch -p arti
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was done using:
for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do
cargo set-version -p $crate 0.31.0
done
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is done using:
cargo set-version --bump patch -p fs-mistrust
cargo set-version --bump patch -p equix
cargo set-version --bump patch -p fslock-guard
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
caret, hashx, oneshot-fused-workaround, retry-error, safelog,
slotmap-careful, and test-temp-dir all only had the change from
88e911acd4bb70bf1da0fc71d77b51cb6abde478 where we bump the rust-version
to 1.83.
Done using:
./maint/bump_nodep retry-error safelog caret hashx test-temp-dir \
slotmap-careful oneshot-fused-workaround
|
| | | | |
|
| |/ /
| |
| |
| | |
Closes #1969.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
* Change return type `Result<Vec<(KeyPath, KeystoreItemType)>>` if favor
of `Result<Vec<StdResult<(KeyPath, KeystoreItemType), UnrecognizedEntryError>>>`
|
| |\
| |
| |
| |
| |
| |
| | |
Fix clippy warnings from nightly rust
Closes #2009
See merge request tpo/core/arti!3008
|
| | |
| |
| |
| | |
clippy nightly complains when the map() output is unused.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.
I have mixed feelings about these warnings: On the plus side,
they really do help to detect functions that are twistier than they
need to be. On the minus side, they get confused by tracing macros,
and the "allows" do pile up. But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
|
| | |
| |
| |
| |
| |
| | |
Clippy nightly detects this problem, though earlier clippy verisons
haven't. The common element here is applying unwrap() to the result
from a write!().
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
dirclient: Stop sending suffix .z in URLs.
See merge request tpo/core/arti!3013
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This suffix is redundant with "Accept-Encoding",
which all Tor directory caches have supported
since 0.3.1.1-alpha.
See torspec#342.
|
| | |
| |
| |
| |
| | |
There's already a check right above the TODO that does what the TODO
asks.
|
| | |
| |
| |
| | |
This addresses one of the TODOs from `reactor::conflux`.
|
