| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit d37824953f9c530c57c8c5936c12b16a829778c3.
Unfortunately, this merge request introduces futures-lite again into the
Cargo.lock generated by maint/downgrade_dependencies. Without this, it
once again caused the same failures in async-fs and
async-global-executor, that were previously fixed before the
above commit landed into main.
This bug is apparently not reproducible on current git main, because the
downgraded Cargo.lock lacks respective dependencies that get
transitively introduced by this (arti!3301) merge request.
|
| |/ /
| |
| |
| |
| |
| |
| | |
```bash
readarray -t publish < <(cargo metadata --format-version 1 | jq -r '.packages[] | select((.id | startswith("path+file:///")) and (.rust_version != null) and (.publish == null or .publish == true or .publish != [])) | .name')
for package in "${publish[@]}"; do echo "$package:"; cargo set-version --bump minor -p "$package"; done
```
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
3 seems like a good number to start with, we can tune it later if
needed.
Fixes: #2207
|
| | |
| |
| |
| |
| |
| | |
I'm not sure I agree with this complaint - it seems like foolish
standards-wonkery - but GNU cp supports -R too and this change will
fix CI on main.
|
| | |
| |
| |
| | |
See https://gitlab.torproject.org/tpo/tpa/team/-/issues/42283
|
| | | |
|
| | |
| |
| |
| | |
As discussed in last week's meeting.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Teach fixup-features to duplicate the modal indentation in an array
Closes #1719
See merge request tpo/core/arti!3317
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If we can't figure out the modal indentation, use " ".
Closes #1719.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
release: Bump versions.
See merge request tpo/core/arti!3311
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
Empirically, this is no longer present in our Cargo.lock.
The problem was fixed upstream, presumably.
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Now that rust nightly has merged doc_auto_cfg into doc_cfg,
and completed https://github.com/rust-lang/rust/pull/138907,
it is no longer necessary.
Closes #1514.
|
| | | |
|
| | |
| |
| |
| | |
Closes #2107
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
maint: Add a check for case-insensitive files
See merge request tpo/core/arti!3207
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Filenames within the tree that exists in multiple versions only
differing by their case cause problems on case-insensitive filesystems.
This commit introduces a simple check that lists all files indexes by
git and searches for duplicate lines while ignoring case during
comparison.
See !3166, #2144
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
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".
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
Ignore RUSTSEC-2025-0052.
Deprecation/removal plan:
https://gitlab.torproject.org/tpo/core/arti/-/issues/2130
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Upgrade various dependencies in preparation for next release
See merge request tpo/core/arti!3188
|
| | |/ / |
|
| |/ /
| |
| |
| | |
Should appease python CI.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
smol: Implement smol in tor-rtcompat
See merge request tpo/core/arti!2986
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
ns-consensus doesn't seem to have ever been released.
This is part of abolishing the use of "ns" to mean "plain".
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
New netdoc parser, with derive macro
See merge request tpo/core/arti!3135
|
| | | |
| | |
| | |
| | |
| | | |
This is a fine API. The representation may change, but that wouldn't
be breaking.
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3125#note_3235240
|
| | | |
| | |
| | |
| | | |
This might avoid some comedy.
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
|
| | | |
|
| | |
| |
| |
| | |
Otherwise we can lose the links from the last item!
|
| | | |
|