| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/ /
| |
| |
| | |
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!
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
cargo-license version 0.7 now normalizes the "-only" variant into
"LGPL-3.0".
|
| | |
| |
| |
| |
| | |
cargo-license 0.7 has started normalizing SPDX expressions, which
includes sorting the licenses in an AND or OR.
|
| | |
| |
| |
| |
| |
| |
| | |
This applies the fixes suggested by shellcheck (the x-prefixes were
causing the `shellcheck` job to fail; see [SC2268]).
[SC2268]: https://www.shellcheck.net/wiki/SC2268
|
| | |
| |
| |
| |
| | |
* arti: raw: `remove-by-path` is now `remove-by-id`
* arti: raw: Adjust integration tests
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* CLI: Add `keys-raw` and subcommand `remove-by-path`
* arti: Add `arti::subcommand::raw` for the CLI `keys-raw`
* tor-keymgr: Add `ArtiNativeKeystoreError::UnexpectedRawEntry`,
`ArtiEphemeralKeystoreError::NotSupported`
* tor-keymgr: Add `tor-keymgr::raw` module
* tor-keymgr: Add `Keystore::remove_unchecked`
* tor-keymgr: Change `Keystore::list` to return `KeystoreEntry`
* tor-keymgr: Add field `KeystoreEntry::raw_id`
* doc: Update keys.md
* doc: Add raw.md
* tor-keymgr: BREAKING: `UnrecognizedEntryError::new` associated
function is now only accessible within the crate `tor-keymgr`
* tor-keymgr: BREAKING: `UnrecognizedEntryId` is renamed to
`UnrecognizedEntry`
* tor-keymgr: BREAKING: `KeyMgr::list()` and `Keystore::list()`
now return `Result<Vec<KeystoreEntryResult<KeystoreEntry>>>`
|
| | |
| |
| |
| | |
Made with https://crates.io/crates/typos-cli
|
| |\ \
| | |
| | |
| | |
| | | |
Update P101 numbers for Q2 2025
See merge request tpo/core/arti!3057
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Update to crunchy 0.2.4, remove exception in reproducible_build
See merge request tpo/core/arti!3073
|
| | |/ /
| | |
| | |
| | | |
This should no longer be necessary.
|
| | | |
| | |
| | |
| | | |
See #2060.
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
With the removal of the hard `rustls` dependency and preferring
`futures-rustls`, then `paste` crate gets downgraded to a too-low of a version
so we should update it for our code to be able to compile correctly.
|
| | |
| |
| |
| | |
Nightly clippy now suggests this.
|
| | |
| |
| |
| |
| | |
The new `cargo-sort` version doesn't like the whitespace we're using to
logically group the workspace members.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Since it's using 1.86 now, there's no reason to downgrade these
packages.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After upgrading to rust:1.86.0-alpine3.21, we got a new error:
```
osxcross: error: cannot find libc++ headers
```
To fix this, we change the linker to
`x86_64-apple-darwin16-clang++-stdc++`.
This invokes some osxcross magic that tells it to find the C++
headers in the stdc++ location... and possibly more.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is sufficient to stop the osxcross errors
``` error: no member named 'lseek64' in the global namespace ```
that we encountered on our earlier attempt to increase our MSRV.
Closes #1335.
|
| |\ \
| | |
| | |
| | |
| | | |
shadow CI tweaks
See merge request tpo/core/arti!2989
|
| | | |
| | |
| | |
| | |
| | | |
It probably makes sense to test against a version of c-tor that we
still support.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Enable --features=full on reproducible builds.
Closes #1964
See merge request tpo/core/arti!2956
|
| | | |
| | |
| | |
| | |
| | | |
This is a workaround for
https://github.com/eira-fransham/crunchy/pull/17
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We generally recommend that people build with --features=full IRL,
so this better matches what we're hoping they come up with.
Additionally, it will help cases like #1964, where packagers would
like to use reproducible builds as inputs to their own packages.
Closes #1964
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix typos
See merge request tpo/core/arti!2961
|