| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
(It is possible for arti-client to have flowctl-cc disabled, but for
tor-proto to have it enabled.)
|
| |
|
|
|
| |
Since we now allow it to be turned on, we can include it among our
supported protocols.
|
| | |
|
| |
|
|
| |
Signed-off-by: David Goulet <[email protected]>
|
| | |
|
| | |
|
| |
|
|
| |
Closes #2012.
|
| |\
| |
| |
| |
| | |
arti-client: Re-export `ConfigurationSources`
See merge request tpo/core/arti!3044
|
| | |
| |
| |
| |
| |
| |
| | |
This commit re-exports `ConfigurationSources` in `arti_client::config`.
The similar `ConfigurationSource` is already publicly exported, but it
unfortunately it is pretty useless without a `ConfigurationSources` to
which it belongs.
|
| | | |
|
| | |
| |
| |
| | |
See #2060.
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
TODO: Implement HasKind trait for TorAddrError
See merge request tpo/core/arti!2965
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit implements the HasKind trait for TorAddrError in address.rs,
mapping all variants to the InvalidStreamTarget error kind. It also updates
the ErrorDetail implementation in err.rs to delegate to TorAddrError's
HasKind implementation instead of hardcoding the error kind.
Resolves TODOs in address.rs and err.rs.
|
| |/
|
|
| |
Done via `./maint/update-release-date`.
|
| | |
|
| |
|
|
|
| |
This name reflects its purpose better than the original one,
since it includes required protocols as well as recommended ones.
|
| |
|
|
|
| |
Also move the comment outside the block it documents,
to prevent a too-long line.
|
| |
|
|
| |
Also wait a little so logs can flush.
|
| | |
|
| | |
|
| |
|
|
|
| |
(This isn't a boolean, because we really don't want people ignoring
all possible required protocols.)
|
| |
|
|
|
|
|
|
|
| |
This doesn't need to be perfect, but we need to use it to see
if a consensus is new enough that we should obey its
recommendations.
This commit also adds a script to update or check our release date,
and calls this script from our cargo-publish script.
|
| | |
|
| |
|
|
| |
This is the major part of #1849.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part of #1849.
Note that these functions are distributed across crates,
so that if (in the future) we stop doing API breaks
with every release, we will get the right outputs.
Note also that these functions build the list of protocols
out of specific symbolic features, rather than numbers:
this makes it easier to avoid errors about "which feature was
Relay=4 again", and easier to avoid accidentally referring to a
protocol that doesn't exist, like "Consensus" (should be "Cons")
or "HsDir" (case is wrong).
|
| |\
| |
| |
| |
| | |
arti-client: Add ErrorDetail::OnionServiceSetup
See merge request tpo/core/arti!2923
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
replace state_dir and storage_mistrust with tor_persist::state_dir::StateDirectory
See merge request tpo/core/arti!2863
|
| | |
| |
| |
| | |
tor_persist::state_dir::StateDirectory
|
| |/
|
|
| |
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Our documentation had dated to an older version of our RPC stream
code, where all streams were automatically optimistic.
But as explained, our use of "optimistic"ness in RPC stream code is
now purely internal, to make it possible to get an DataStreamCtrl.
This isn't user-visible in our rpc_conn_open_stream code.
Closes #1583
|
| |\
| |
| |
| |
| | |
clippy: deny `mod_module_files`
See merge request tpo/core/arti!2689
|
| | |
| |
| |
| |
| |
| | |
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
|
| |/ |
|
| |
|
|
|
| |
This time, we make explicit that it is a _base_ resolver,
and that it is client-only.
|
| |
|
|
|
|
|
|
| |
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Rather than using `arti_client::config::path_resolver()`, third-party
code can get the path resolver using `TorClientConfig`s
`AsRef<CfgPathResolver>` impl instead.
|
| | |
|
| |
|
|
| |
Also updated to use the `PATH_RESOLVER` resolver.
|