vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/crates/tor-circmgr/Cargo.toml

99 lines
3.5 KiB
TOML
Raw Permalink Normal View History

Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
[package]
name = "tor-circmgr"
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
version = "0.10.0"
Add the tor project as an author.
2021-03-17 18:43:40 +00:00
authors = ["The Tor Project, Inc.", "Nick Mathewson <nickm@torproject.org>"]
Bump every crate's edition to 2021. This is an automated change made with a perl one-liner and verified with grep -L and grep -l. Some warnings are introduced with this change; they will be removed in subsequent commits. See arti#208 for older discussion on this issue.
2022-04-25 17:19:02 +01:00
edition = "2021"
Increment MSRV to 1.65 in every crate.
2023-04-11 20:31:12 +01:00
rust-version = "1.65"
Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
license = "MIT OR Apache-2.0"
Give it a homepage everyplace.
2021-03-17 18:13:26 +00:00
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
Add a description field to all our Cargo.toml files
2021-03-17 18:31:59 +00:00
description = "Manage a set of anonymous circuits over the Tor network"
Reformat tor-circmgr/Cargo.toml
2022-03-25 19:12:17 +00:00
keywords = ["tor", "arti", "async"]
categories = ["network-programming", "cryptography"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
circmgr: Add a function to build a circuit by path Public function so an application can use to build a circuit using a custom path. Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-04-01 18:58:03 +01:00
[features]
Add "full" and "experimental" features to arti-client and below. The "full" feature is a catch-all for all features, _except_: * Those that select a particular implementation (like tor-llcrypto/with-openssl) or build flag (like "static") * Those that are experimental or unstable (like "experimental-api") * Those that are testing-only.
2022-06-10 20:26:51 +01:00
circmgr: Make "specific-relay" non-experimental.
2022-11-16 17:35:01 +00:00
default = []
Reformat Cargo.toml files.
2023-05-15 13:34:47 +01:00
full = [
Mark all {hs,onion-serivce}-client features as non-experimental.
2023-06-29 18:09:37 +01:00
"hs-client",
Reformat Cargo.toml files.
2023-05-15 13:34:47 +01:00
"specific-relay",
"retry-error/full",
"safelog/full",
"tor-basic-utils/full",
"tor-chanmgr/full",
"tor-config/full",
"tor-error/full",
"tor-guardmgr/full",
"tor-hscrypto?/full",
"tor-linkspec/full",
"tor-netdir/full",
"tor-netdoc/full",
"tor-persist/full",
"tor-proto/full",
"tor-rtcompat/full",
]
circmgr: Make "specific-relay" non-experimental.
2022-11-16 17:35:01 +00:00
specific-relay = []
tor-circmgr: Provide testing feature and TestConfig Like the similar thing in tor-guardmgr.
2023-02-23 17:24:43 +00:00
# Enable testing-only APIs. APIs under this feature are not
# covered by semver.
Revise all XXXXs from fixup-features
2023-05-15 16:00:28 +01:00
testing = ["tor-guardmgr/testing", "__is_experimental"]
tor-circmgr: Provide testing feature and TestConfig Like the similar thing in tor-guardmgr.
2023-02-23 17:24:43 +00:00
Document that the "experimental-api" feature is not semver-covered.
2021-11-11 15:44:24 +00:00
# Enable experimental APIs that are not yet officially supported.
#
# These APIs are not covered by semantic versioning. Using this
# feature voids your "semver warrantee".
Mark all {hs,onion-serivce}-client features as non-experimental.
2023-06-29 18:09:37 +01:00
experimental = ["experimental-api", "hs-service", "testing"]
Run fixup-features --no-annotate for initial Cargo.toml fixes. This does the following: - Gives every crate a `full`. - Cause every `full` to depend on `full` from the lower-level crates. - Makes every feature listed _directly_ in `experimental` depend on `__is_experimental`.
2023-05-15 13:16:43 +01:00
experimental-api = ["visibility", "__is_experimental"]
Mark all {hs,onion-serivce}-client features as non-experimental.
2023-06-29 18:09:37 +01:00
hs-client = ["hs-common"]
Run fixup-features --no-annotate for initial Cargo.toml fixes. This does the following: - Gives every crate a `full`. - Cause every `full` to depend on `full` from the lower-level crates. - Makes every feature listed _directly_ in `experimental` depend on `__is_experimental`.
2023-05-15 13:16:43 +01:00
hs-service = ["hs-common", "__is_experimental"]
Rename onion-* cargo features to hs-* in tor-* crates Fixes #756
2023-02-24 14:26:25 +00:00
hs-common = ["tor-hscrypto"]
Run fixup-features --no-annotate for initial Cargo.toml fixes. This does the following: - Gives every crate a `full`. - Cause every `full` to depend on `full` from the lower-level crates. - Makes every feature listed _directly_ in `experimental` depend on `__is_experimental`.
2023-05-15 13:16:43 +01:00
__is_experimental = []
circmgr: Add a function to build a circuit by path Public function so an application can use to build a circuit using a custom path. Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-04-01 18:58:03 +01:00
Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
[dependencies]
HS configuration: Add retry parameters to configuration I think these should go in `[circuit_timing]`. That section already has some retry parameters, so is not strictly *timing*. This is not honoured yet.
2023-06-23 16:58:08 +01:00
amplify = { version = "4", default-features = false, features = ["derive"] }
Upgrade async-trait requirement to 1.54 We need the fix from [82d69902], which first appeared in async-trait version 1.54. (Technically we only need this fix in tor-hsclient, but we may as well update our minimal async-trait version everywhere.) [82d69902]: https://github.com/dtolnay/async-trait/commit/82d69902535f5cb7f5d9e1ea4168c64abd496389
2023-06-12 18:12:34 +01:00
async-trait = "0.1.54"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
bounded-vec-deque = "0.1"
Switch to derive_builder_arti_fork For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
2022-05-06 13:18:03 +01:00
derive_builder = { version = "0.11.2", package = "derive_builder_fork_arti" }
tor-circmgr: Provide testing feature and TestConfig Like the similar thing in tor-guardmgr.
2023-02-23 17:24:43 +00:00
derive_more = "0.99.3"
use downcast-rs instead of our own AsAny
2022-03-12 10:10:00 +00:00
downcast-rs = "1.2.0"
replace Arc with Box and use dyn-clone this also removes JoinResult
2022-03-12 17:33:25 +00:00
dyn-clone = "1.0.4"
Replace manual Debug impl with educe in tor-circmgr
2022-03-02 14:32:29 +00:00
educe = "0.4.6"
Upgrade required version of futures crate to 0.3.14 Earlier versions have a bug in UnboundedReceiver that make our new dirclient tests fail.
2022-01-28 19:50:03 +00:00
futures = "0.3.14"
humantime: Update to humantime-serde 1.1.1 This has the humantime_serde::option module, which we have upstreamed and are about to switch to. The remaining dependency with version = "1" is going to be removed in a moment.
2022-03-11 17:24:21 +00:00
humantime-serde = "1.1.1"
Upgrade to itertools 0.11.0 The breaking changes here do not seem to affect us.
2023-06-26 14:30:54 +01:00
itertools = "0.11.0"
Turn FallbackList into a real type, and store one in GuardMgr. The guard manager is responsible for handing out the first hops of tor circuits, keeping track of their successes and failures, and remembering their states. Given that, it makes sense to store this information here. It is not yet used; I'll be fixing that in upcoming commits. Arguably, this information no longer belongs in the directory manager: I've added a todo about moving it. This commit will break compilation on its own in a couple of places; subsequent commits will fix it up.
2022-03-25 20:44:12 +00:00
once_cell = "1"
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
pin-project = "1"
rand = "0.8"
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
retry-error = { path = "../retry-error", version = "0.5.0" }
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
safelog = { path = "../safelog", version = "0.3.2" }
Minimize the required version for each dependency. I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.
2022-01-07 20:54:24 +00:00
serde = { version = "1.0.103", features = ["derive"] }
static_assertions = "1"
thiserror = "1"
Increment patchlevel versions of crates with minor changes These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```
2023-08-01 15:57:55 +01:00
tor-basic-utils = { path = "../tor-basic-utils", version = "0.7.3" }
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
tor-chanmgr = { path = "../tor-chanmgr", version = "0.10.0" }
Increment patchlevel versions of crates with minor changes These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```
2023-08-01 15:57:55 +01:00
tor-config = { path = "../tor-config", version = "0.9.3" }
tor-error = { path = "../tor-error", version = "0.5.3", features = ["tracing"] }
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
tor-guardmgr = { path = "../tor-guardmgr", version = "0.10.0" }
Bump minor versions on crates with breaking changes Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```
2023-06-30 13:38:16 +01:00
tor-hscrypto = { path = "../tor-hscrypto", version = "0.3.0", optional = true }
Increment patchlevel versions of crates with minor changes These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```
2023-08-01 15:57:55 +01:00
tor-linkspec = { path = "../tor-linkspec", version = "0.8.2" }
tor-netdir = { path = "../tor-netdir", version = "0.9.3" }
tor-netdoc = { path = "../tor-netdoc", version = "0.8.2" }
tor-persist = { path = "../tor-persist", version = "0.7.3" }
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
tor-proto = { path = "../tor-proto", version = "0.12.0" }
Bump crate versions in preparation for v1.1.5 release. Generated with the following commands: ``` cargo set-version --bump minor -p tor-cell cargo set-version --bump minor -p tor-linkspec cargo set-version --bump minor -p tor-proto cargo set-version --bump minor -p tor-netdoc cargo set-version --bump minor -p tor-circmgr cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-basic-utils cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-hscrypto cargo set-version --bump patch -p tor-checkable cargo set-version --bump patch -p tor-async-utils cargo set-version --bump patch -p caret cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-rtcompat cargo set-version --bump patch -p tor-rtmock cargo set-version --bump patch -p tor-protover cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-socksproto cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-congestion cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p tor-chanmgr cargo set-version --bump patch -p tor-ptmgr cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-hsclient cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p arti-rpcserver cargo set-version --bump patch -p arti-config cargo set-version --bump patch -p arti-hyper cargo set-version --bump patch -p arti cargo set-version --bump patch -p arti-bench cargo set-version --bump patch -p arti-testing ```
2023-06-01 15:03:05 +01:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.9.1" }
Upgrade tracing to 0.1.36. This is the first version to impl Value for String. With luck, this will get minimal_versions CI passing.
2023-05-03 15:08:24 +01:00
tracing = "0.1.36"
circmgr: Declare builder() unconditionally. (Still, only expose it when experimental-api is enabled.)
2023-03-16 17:06:18 +00:00
visibility = { version = "0.0.1", optional = true }
Enormous tor-circmgr rewrite. As with the tor-chanmgr code, the circuit manager is now implemented using an AbstractCircMgr type that uses traits to abstract the particular behavior of other types that it uses. (Specifically: circuits, building circuits, and telling whether one circuit usage is compatible with another.) Abstracting out the dependencies in this ways makes it possible to test the circuit manager without having to actually build real circuits. This commit also introduces new behavior for handling pending circuit requests. Upon getting a new request, first we check to see if there's an existing circuit we can use. If there isn't, we look for pending circuits and wait for them. If there aren't any pending circuits we can use, we launch one or more, and wait for them. So far, that's the same as the old behavior. But here's a change: if, while we are waiting for some pending circuits, a different circuit is completed, and it's one we could use, then the task that was building _that_ circuit will tell us: "please look at this circuit". This gives us better changes of getting a usable circuit fast. Minor changes: * The Error type in CircMgr no longer uses anyhow; several errors have been simplified. * We've gotten more formal about the relationship between circuit usage and target usage.
2021-05-27 20:48:30 +01:00
weak-table = "0.3.0"
Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
[dev-dependencies]
futures-await-test = "0.3.0"
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
tor-guardmgr = { path = "../tor-guardmgr", version = "0.10.0", features = ["testing"] }
Bump patchlevel versions on crates with smaller changes Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```
2023-06-30 13:42:21 +01:00
tor-llcrypto = { path = "../tor-llcrypto", version = "0.5.2" }
Increment patchlevel versions of crates with minor changes These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```
2023-08-01 15:57:55 +01:00
tor-netdir = { path = "../tor-netdir", version = "0.9.3", features = ["testing"] }
tor-persist = { path = "../tor-persist", version = "0.7.3", features = ["testing"] }
Bump crate versions in preparation for v1.1.5 release. Generated with the following commands: ``` cargo set-version --bump minor -p tor-cell cargo set-version --bump minor -p tor-linkspec cargo set-version --bump minor -p tor-proto cargo set-version --bump minor -p tor-netdoc cargo set-version --bump minor -p tor-circmgr cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-basic-utils cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-hscrypto cargo set-version --bump patch -p tor-checkable cargo set-version --bump patch -p tor-async-utils cargo set-version --bump patch -p caret cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-rtcompat cargo set-version --bump patch -p tor-rtmock cargo set-version --bump patch -p tor-protover cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-socksproto cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-congestion cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p tor-chanmgr cargo set-version --bump patch -p tor-ptmgr cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-hsclient cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p arti-rpcserver cargo set-version --bump patch -p arti-config cargo set-version --bump patch -p arti-hyper cargo set-version --bump patch -p arti cargo set-version --bump patch -p arti-bench cargo set-version --bump patch -p arti-testing ```
2023-06-01 15:03:05 +01:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.9.1", features = ["tokio", "native-tls"] }
Update minor versions on crates that have had breaking changes These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
2023-08-01 15:51:25 +01:00
tor-rtmock = { path = "../tor-rtmock", version = "0.9.0" }
enable doc_auto_cfg feature on every crate when documenting for docs.rs
2022-08-17 20:13:13 +01:00
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]