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

49 lines
1.7 KiB
TOML
Raw Normal View History

arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
[package]
name = "arti-testing"
Bump all arti*, tor* crates to 0.2.0 Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
2022-04-01 14:15:18 +01:00
version = "0.2.0"
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +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"
Add 'rust-version = "1.56"' to every Cargo.toml file. This change was made automatically with a perl one-liner, and confirmed with `grep -L`. The `rust-version` field itself was introduced in 1.56.0.
2022-04-25 17:10:41 +01:00
rust-version = "1.56"
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
license = "MIT OR Apache-2.0"
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
description = "Tools for testing the Arti Tor implementation."
keywords = ["tor", "arti", "privacy", "anonymity"]
categories = ["command-line-utilities", "cryptography"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
publish = false
[features]
[dependencies]
Reformat all not-yet-reformatted Cargo.toml files. There are no semantic changes here; only formatting. This is in preparation for other changes (wrt MSRV and edition)
2022-04-25 17:03:41 +01:00
arti = { package = "arti", path = "../arti", version = "0.2.0" }
Bump all arti*, tor* crates to 0.2.0 Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
2022-04-01 14:15:18 +01:00
arti-client = { package = "arti-client", path = "../arti-client", version = "0.2.0", features = [
Directory filtering in arti-testing. This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
2022-03-30 13:48:35 +01:00
"dirfilter",
] }
Bump all arti*, tor* crates to 0.2.0 Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
2022-04-01 14:15:18 +01:00
tor-dirmgr = { package = "tor-dirmgr", path = "../tor-dirmgr", version = "0.2.0", features = [
Directory filtering in arti-testing. This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
2022-03-30 13:48:35 +01:00
"dirfilter",
] }
Bump all arti*, tor* crates to 0.2.0 Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
2022-04-01 14:15:18 +01:00
tor-netdoc = { package = "tor-netdoc", path = "../tor-netdoc", version = "0.2.0", features = [
Directory filtering in arti-testing. This feature allows us to detect different failing cases for arti#329 that would otherwise be hard to induce. It works by filtering consensus directory objects and/or microdescriptor objects before introducing them to the directory manager. Closes #397.
2022-03-30 13:48:35 +01:00
"experimental-api",
"dangerous-expose-struct-fields",
] }
Bump all arti*, tor* crates to 0.2.0 Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
2022-04-01 14:15:18 +01:00
tor-checkable = { path = "../tor-checkable", version = "0.2.0", features = ["experimental-api"] }
Reformat all not-yet-reformatted Cargo.toml files. There are no semantic changes here; only formatting. This is in preparation for other changes (wrt MSRV and edition)
2022-04-25 17:03:41 +01:00
tor-rtcompat = { path = "../tor-rtcompat", version = "0.2.0" }
tor-error = { path = "../tor-error", version = "0.2.0" }
arti-config = { path = "../arti-config", version = "0.2.0" }
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
anyhow = "1.0.23"
async-trait = "0.1.2"
config = { version = "0.12.0", default-features = false }
cfg-if = "1.0.0"
futures = "0.3.14"
tracing = "0.1.18"
notify = "4.0"
pin-project = "1"
arti-testing: Initial support for broken TCP. This commit adds support for a BrokenTcp provider that can make connection attempts fail or time out. It doesn't yet have a way to turn on the failure.
2022-03-04 22:43:17 +00:00
rand = "0.8"
Downgrade `rlimit` to 0.7. Upstream 0.8.2 has broken compilation with Rust 1.53; versions 0.8.{0,1} have been yanked. Possibly by the time the next arti version comes out, they'll have fixed this situation, or we'll have upgraded our MSRV. Upstream issue at https://github.com/Nugine/rlimit/issues/42 .
2022-04-06 15:21:33 +01:00
rlimit = "0.7"
arti-testing: Initial implementation This commit adds a new program to try to implement the ideas behind experimentation in arti#329. In particular, it tries to implement basic client "can I bootstrap and connect" functionality testing, with a lot of instrumentation, and support for breaking things. So far, the instrumentation is limited to counting TCP bytes and connections, and counting events. Still, this is enough to measure behavior on some of the incorrect-clock tests. NOTE: For now, you are _required_ to pass in an explicit configuration, in hopes that this will lead you to override your storage directories for doing specific experiments.
2022-03-02 15:03:19 +00:00
serde = { version = "1.0.103", features = ["derive"] }
tracing-subscriber = { version = "0.3.0", features = ["env-filter"] }
tokio = { version = "1.7", features = ["signal", "macros"] }
clap = "2.33.0"
tracing-appender = "0.2.0"