| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Only two links so far. Most of the xrefs will be made into proper
syntax later.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vanguards: Make client rend circuits be STUB+.
Closes #1474
See merge request tpo/core/arti!2230
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This updates the code to match the spec.
This fixes TROVE-2024-008.
Closes #1474
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
According to the [vanguards spec], client rendezvous circuits should be
STUB+:
* lite: `C -> G -> L2 -> Rend`
* full: `C -> G -> L2 -> L3 -> Rend`
[vanguards spec]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/e5ace3667dcbbf893c6b632fd4e3f16114fd2a0e/spec/vanguards-spec/index.md
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix macos build test by bodging the Cargo.lock
Closes #1472
See merge request tpo/core/arti!2234
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Hopefully this will not be too slow.
Fixes #1472.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit a6801c10584558316ff38f354167812d0c697549.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As proposed in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2231#note_3043322
I made this commit by:
* Taking the hunk to add `cc = "1.0.93"` from !2231.
* Running `cargo fetch`
* Staging everything except the additions of cc
to `Cargo.toml` and `Cargo.lock`
Here is the output I got from cargo:
Updating crates.io index
Locking 5 packages to latest compatible versions
Downgrading addr2line v0.22.0 -> v0.21.0 (latest: v0.23.0)
Downgrading backtrace v0.3.73 -> v0.3.71 (latest: v0.3.73)
Downgrading cc v1.0.100 -> v1.0.93 (latest: v1.0.101)
Downgrading gimli v0.29.0 -> v0.28.1 (latest: v0.30.0)
Downgrading object v0.36.0 -> v0.32.2 (latest: v0.36.0)
Downloaded cc v1.0.93
Downloaded derive-deftly v0.13.1
Downloaded 2 crates (149.8 KB) in 1.52s
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Update to derive-deftly 0.13.1
See merge request tpo/core/arti!2232
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes build breakage in the build-repro test.
derive-deftly 0.13.0 has an MSRV violation, due to a breach by cargo
of the Rust stability guarantee: d-d 0.13.0 works with Rust 1.56 but
not 1.76.
References:
https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/issues/103
https://github.com/rust-lang/cargo/issues/14147#issuecomment-2189915460
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove arti-hyper
See merge request tpo/core/arti!2225
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This has been obsolete for a very long time.
We have already published a version with a "won't be updated" warning.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Run maint/fixup-features
See merge request tpo/core/arti!2229
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Precisely
nailing-cargo -Eu run -p fixup-features Cargo.toml
These changes are just `full` propagation. Note the `?` in the
arti-relay propagation, which is essential: we don't actually *enable*
arti-relay at all, with this.
Also, there is a formatting anomaly, which I'll fix in a moment.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Routine dependency updates
See merge request tpo/core/arti!2228
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No code changes needed.
Precisely
nailing-cargo -Eu upgrade --incompatible -p base32
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No code changes needed.
Precisely
nailing-cargo -Eu upgrade --incompatible -p statrs
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No code changes needed.
Precisely
nailing-cargo -Eu upgrade --incompatible -p itertools
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We're about to update to iterools 0.13.0. We must therefore have a
version of strum which is not affected by
https://github.com/Peternator7/strum/issues/358
Precisely
git-grep -l '^strum' | xargs perl -i~ -pe 's{"0\.26"}{"0.26.3"}'
No changes to lockfile - we're already using 0.26.3, except perhaps in
the minimal versions test.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No code changes needed.
Precisely
nailing-cargo -Eu upgrade --incompatible -p derive-deftly
|
| |/ / /
| | |
| | |
| | |
| | | |
Precisely
cargo update
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Disable macos build tests
See merge request tpo/core/arti!2226
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rename OptTimestamp to AtomicOptTimestamp
Closes #1412
See merge request tpo/core/arti!2218
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Turn crate ownership discrepancies into a warning
See merge request tpo/core/arti!2220
|
| |/ /
| |
| |
| |
| | |
Ideally we'd tolerate situations with unaccepted ownership requests,
but that information doesn't seem to be public.
|
| |\ \
| | |
| | |
| | |
| | | |
Resolve a rustdoc warning.
See merge request tpo/core/arti!2215
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Write a README for tor-rpcbase
See merge request tpo/core/arti!2210
|
| | | |/
| |/| |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Better crate ownership check, and run it in CI
See merge request tpo/core/arti!2201
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is superseded now.
(I wish I had noticed it; perhaps I could have souped it up rather
than writing a whole new thing, but I think the result would have been
much the same.)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I think that the effect of this will be as follows:
* MR branches will never run this, so when the crate ownership
is wrong, development can continue.
* When a new crate is first published, it will transition from
"ignored" to "complaining". This will happen on the first
CI run on main after "cargo publish" is run. But it *won't*
happen on the CI run on the publication tag.
The intent is that we discover a failure to `git add` while the
release technician who published the new crate is still around.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Compared to check-crate-owners:
1. Checks for uniformity, rather than having an embedded list
of intended maintainers.
2. Uses curl | jq, rather than `cargo owner`.
This is necessary for:
3. Ignores crates which have never been published.
This is necessary to be able to run this in CI, since there
may be new crates in the workspace.
4. Prints the ownership information rather differently -
just the usernames. This is a consequence of using curl | jq.
|
| | | |
| | |
| | |
| | | |
This is useful for debugging.
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
We (will) use `*.sh` for shell include files. We're about to make one
of these.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
TorClientBuilder: Add the ability to retry when fslock fails
Closes #1464
See merge request tpo/core/arti!2198
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Name chosen to match the error kind that we're detecting.
|
| | | |
|