| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
CI: increase test-transfer sizes
See merge request tpo/core/arti!3047
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With the increased transfer sizes and simulation run-time,
the previous log levels resulted in excessively large log files.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is the transfer size used in the tor CI chutney tests, to
more-fully exercise SENDMEs / congestion control.
We also increase the simulation run time to allow time for the larger
transfers.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
proto: Use allow(unused) instead of expect(unused).
See merge request tpo/core/arti!3213
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With rustc 1.85, this `expect(unused)` triggers a "lint expectation
unfulfilled" error, because rust thinks the struct *is* used (because of
the d-d `TryFrom` implementation), despite the fact that it's never
actually constructed. This isn't a problem on newer versions (it's
correctly identified as unused/dead code on 1.89, for example).
Using `allow` instead of `expect` is slightly less nice, but it makes
`clippy` pass on 1.85 too.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
fix documentation for StreamPrefs::connect_to_onion_services to match changes in !2506
Closes #2145
See merge request tpo/core/arti!3212
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
changes in !2506
Signed-off-by: Aiden McClelland <[email protected]>
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Release.md: Tweak one of the checklist items
See merge request tpo/core/arti!3211
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I almost declared completion too early, since I had written
(but not published) a blogpost.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
Remove semver.md files post v1.5.0
See merge request tpo/core/arti!3210
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Changelog for 1.5.0
See merge request tpo/core/arti!3204
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Our MSRV policy says that we won't bump the MSRV in a patchlevel
release.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Manually correct hjrgrn's name, and remove duplicate for nield.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will lower the odds that we accidentally welcome the
(placeholder name) "Alyssa P. Hacker" as a new team member.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Version bumps for arti 1.5.0
See merge request tpo/core/arti!3206
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We've promised in our README not to bump MSRV in patchlevel
releases. So now this is 1.5.0.
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Per policy, we bump the minor version of every tor-*, arti-* crate
on each release.
We have updated our MSRV, so we're treating this as a breaking
change for our non-(arti/tor)-prefixed crates too.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
Run "update-release-date"
See merge request tpo/core/arti!3208
|
| |/ / / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Run "cargo update" in preparation for release.
See merge request tpo/core/arti!3201
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Upgrade to criterion 0.7
Closes #2026
See merge request tpo/core/arti!3199
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Closes #2026.
We can do this now that criterion-cycles-per-byte has also upgraded.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Run "fixup-features" in preparation for release.
See merge request tpo/core/arti!3196
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use the v3 dependency resolver.
Closes #2135
See merge request tpo/core/arti!3183
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(This is the default for Rust 2024.)
Closes #2135.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
proto: Small reorg moving impl-agnostic types out of client
See merge request tpo/core/arti!3193
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The `TunnelId*` types will be reused in the relay reactor (exit relays
need to have the concept of a "tunnel ID" because of conflux).
Now the `relay::reactor` module only has a single import from `client`
(for the `unwrap_or_shutdown` helper, which we should be able to remove
soon). From now, we will avoid importing anything from `client` in the
`relay` module, and instead prefer refactoring the code as needed (to
pull the implementation-agnostic parts outside of `client`).
This commit has no functional changes, just code motion.
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This is just code motion (I suggest reviewing with `--color-moved`).
This also moves the implementation-agnostic parts from
`tor_proto::client::circuit` to a new `tor_proto::circuit` module.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
proto: Add a new RelayCircChanMsg message subclass.
See merge request tpo/core/arti!3198
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This will be used to restrict the types of messages that can be sent on
the relay-specific channels.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This enables us to remove the open-coded implementations in favor of the
derived version.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The code for generating these is repetitive (see `CreateResponse` and
`ClientChanMsg`), and we will soon need a `RelayChanMsg` type too, so
now is a good time to introduce a helper for generating the boilerplate.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Fix up some license exceptions in check_licenses scipt.
See merge request tpo/core/arti!3195
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Instead of using a specific "if" for each license/crate combo (as we
had done for priority-queue) or adding a blanket exception (as we
had done for ring and aws-lc-sys) we now use an associative array to
indicate that a license is allowed for a single crate.
|
| | | | | | | | | | |
|
| | | |_|/ / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | | |
Ring is now "Apache-2.0 AND ISC".
|