| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.40.0
done
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The non-{arti-,tor-} crates are:
```
./maint/list-crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
futures-copy
```
Because this release bumps the MSRV, I am bumping the minor version of all of
them.
MINOR="
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
futures-copy
"
for crate in $MINOR; do
cargo set-version --bump minor -p $crate;
done
```
|
| |
|
|
|
|
|
|
|
| |
`clippy::collapsible_if` started triggering after bumping the MSRV to
1.88.
Since this triggers from a lot of places, and since there even are a
couple of instances where we explicitly allow `clippy::collapsible_ifs`,
I've opened #2342 for deciding what to do about it.
|
| |
|
|
|
|
|
| |
As agreed at our last team meeting.
See
https://gitlab.torproject.org/tpo/core/arti/#minimum-supported-rust-version
|
| |
|
|
|
|
| |
This enables us to un-ignore RUSTSEC-2026-0009.
See #2341 for analysis of impact.
|
| |\
| |
| |
| |
| |
| |
| | |
downgrade-dependencies: require async-io 1.1.5.
Closes #1168
See merge request tpo/core/arti!3660
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In my testing, this appears to fix #1168, an intermittent test
failure. The underlying cause of the failure appears to be
a surprise blocking return old async-io versions:
> The problem was in that random yielding inside
> AsyncRead/AsyncWrite (which is supposed to prevent task starvation
> when I/O never returns the WouldBlock error) doesn't play nice
> with the TLS protocol. It seems that TLS handshake fails if a
> write errors with WouldBlock.
-- https://github.com/smol-rs/async-io/issues/31
I think the problem here might actually be something more subtle
than _that_, since WouldBlock on an underlying write is totally
legit. But this appears to fix the testing issue at least.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Set package.metadata.docs.rs.all-features to true for all crates
Closes #2307
See merge request tpo/core/arti!3656
|
| | |/
| |
| |
| |
| |
| | |
All (publishable) crates should explicitly configure what features to (not) document in docs.rs.
This to avoid our documentation containing references to public API specifications which yield "given resource not found"
due to them being behind a feature flag not being published to docs.rs by default.
|
| |/
|
|
|
| |
See
https://gitlab.torproject.org/tpo/core/arti/-/issues/2341#note_3339657
|
| |
|
|
|
|
|
|
|
|
| |
Done via:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.39.0
done
```
|
| |\
| |
| |
| |
| | |
fix(minver): Update paste dependency to be minver compatible
See merge request tpo/core/arti!3610
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This adds the lint to all our crates.
|
| |/
|
|
| |
Part of #2328
|
| | |
|
| |
|
|
|
|
|
| |
Change the script name to use hyphens, not underscores.
Make the script name and the CI job name the same, except the script
has -arti at the end in case we add more similar checks.
|
| |
|
|
| |
This avoids tripping over things like `__pycache__`
|
| |
|
|
|
|
|
|
|
|
| |
Swap the symlink direction: now we have list_crates.py (the python
module) with a symlink list-crates pointing to it. This allows the
module to be imported but the command to be kebab case.
The checking tooling doesn't understand this special arrangement.
Lots of references to update!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We're using maint/common/shellcheck-all now. The docs were
inconsistent.
|
| |
|
|
| |
We had both maint/docker-... and maint/docker_...
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Use kebab case, and also add the word deps. Otherwise it might refer
to files or something.
|
| | |
|
| |
|
|
|
|
| |
The job was called `check-targets` and the script was called
`cargo_check_target`. Make them match. Use kebab case, and the
plural (it checks multiple targets).
|
| |\
| |
| |
| |
| |
| |
| | |
maint: Use 'C.UTF-8' locale for sorting `exclude_contributors.txt`
Closes #2313
See merge request tpo/core/arti!3588
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make all non-main APIs in arti experimental.
Closes #2284, #2299, and #419
See merge request tpo/core/arti!3586
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Only fn main() is now pub when experimental-api is disabled.
Closes #2284.
|
| | |/
| |
| |
| |
| | |
We'll use this to enforce the opacity of the arti crate, once it is
more opaque.
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bincode is unmaintained. Right now, we do not depend on it directly,
but rather transitively through maybenot (with tor-proto) and
typed-index-collections (with tor-netdoc).
This has been reported upstream in the respective crates:
* <https://github.com/zheland/typed-index-collections/issues/10>
* <https://github.com/maybenot-io/maybenot/issues/40>
It is pretty unfortunate, but there is not much we can do at the current
moment, given that it is an external matter and we need it for the next
arti release; also, as far as I am aware, there are no known security
vulnerabilities in the current version of bincode.
Therefore, this commit adds it to the list of exception.
Fixes #2311
See #2312
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Technically `priority-queue` belongs in the `MPL_20_OK` list, but our
current checks are too rudimentary to be able to handle the `OR` (we
*do* split on `OR` for one of the checks, but we only compare the
resulting licenses against `RECOGNIZED_LICENSES`, not `MPL_20_OK`). So
for now, let's retain the exception for `priority-queue`.
(We could expand the logic in the branch handling the `OR'`d licenses to
fix this issue, but the result would be quite fragile; and besides, I
think we're going to eventually want to replace this with a proper
license parser).
|
| |
|
|
|
|
|
|
|
|
|
| |
They have in fact added the MPL "Exhibit A" text to every file in the
crate.
The license is still LGPL-3.0-or-later OR MPL-2.0, so the rest of the
comment still applies.
See
https://github.com/garro95/priority-queue/pull/54/commits/e2f90b0811c252f80165bbdb19233464289e428f
|
| |
|
|
| |
Do less parsing, and instead interpose the mistune internals.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
`InlineParser::parse_link` isn't publicly documented, so may be subject
to more breakage.
|