| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit adds a parameter to TorClientBuilder that control how long
we should retry constructing a TorClient if we get a
LocalResourceInUse error. When this parameter is not set, we
default to 500 milliseconds for async entry points and 0
milliseconds for sync entry points.
(`LocalResourceInUse` usually means that a lockfile is held by
somebody else; but when the resource is some other type, we
typically want the same behavior anyway.)
(I really don't want to introduce delays by default for the
create_unbootstrapped case, since it previously had no delay at
all.)
There is now also an async entry point to create an unbootstrapped
TorClient.
Closes #1464.
|
| |/
|
|
|
| |
There is no actual reason to consume this type, and taking it by
reference allows us to retry.
|
| |\
| |
| |
| |
| |
| |
| | |
tor-circmgr: Refactor VanguardHsPathBuilder::pick_path
Closes #1459
See merge request tpo/core/arti!2205
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This is just code motion: moving the vanguard-specific parts of
`maybe_extend_stub_circuit()` behind the `vanguards` feature will enable
us to refactor it to use `select_middle_for_vanguard_circuit()`, which
is only available if the `vanguards` feature is enabled.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is a follow up from https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2186#note_3035525
Closes #1459
|