zecfoundation
/
zebra
mirror of https://github.com/ZcashFoundation/zebra.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zebra/zebra-network/Cargo.toml

46 lines
1.3 KiB
TOML
Raw Normal View History

Create workspace skeleton based on design.md
2019-08-29 14:46:54 -07:00
[package]
name = "zebra-network"
Update versions for zebra v1.0.0-alpha.14 release (#2537) Co-authored-by: teor <teor@riseup.net>
2021-07-29 12:42:21 -07:00
version = "1.0.0-alpha.14"
Fix authorship, license information. (#55) * Fix authorship, license information. I *thought* I had done a sed pass over the Cargo defaults when doing repository initialization, but I guess I missed it or something. Anyways, fixed now.
2019-10-08 09:25:59 -07:00
authors = ["Zcash Foundation <zebra@zfnd.org>"]
license = "MIT OR Apache-2.0"
Create workspace skeleton based on design.md
2019-08-29 14:46:54 -07:00
edition = "2018"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
Replace PeerServices(u64) with a bitflags struct. This gives considerably better ergonomics.
2019-09-30 11:58:32 -07:00
bitflags = "1.2"
build(deps): bump byteorder from 1.3.4 to 1.4.2 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.3.4 to 1.4.2. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.3.4...1.4.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-11 02:01:37 -08:00
byteorder = "1.4"
deps: move to tokio 0.3, tower 0.4 This change is mostly mechanical, with the exception of the changes to the `tower-batch` middleware. This middleware was adapted from `tower::buffer`, and the `tower::buffer` code was changed to implement its own bounded queue, because Tokio 0.3 removed the `mpsc::Sender::poll_send` method. See https://github.com/tower-rs/tower/commit/ddc64e8d4d4d499adef569e284f317288edd6513 for more context on the Tower changes. To match Tower as closely as possible in order to be able to upstream `tower-batch`, those changes are copied from `tower::Buffer` to `tower-batch`.
2020-11-19 11:54:20 -08:00
bytes = "0.6"
Replace Timestamp with chrono::DateTime<Utc>
2019-09-11 19:24:16 -07:00
chrono = "0.4"
Implement custom Debug for Magic types Related to #63
2019-10-15 16:38:44 -07:00
hex = "0.4"
# indexmap has rayon support for parallel iteration,
Beginning of peerset implementation. (#62) * Don't expose submodules of zebra_network::peer. * PeerSet, PeerDiscover stubs. Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> * Initial work on PeerSet. This is adapted from the MIT-licensed tower-balance implementation. * Use PeerSet in the connect stub.
2019-10-10 18:15:24 -07:00
# which we don't use, so disable it to drop the dependencies.
build(deps): bump indexmap from 1.6.2 to 1.7.0 Bumps [indexmap](https://github.com/bluss/indexmap) from 1.6.2 to 1.7.0. - [Release notes](https://github.com/bluss/indexmap/releases) - [Commits](https://github.com/bluss/indexmap/compare/1.6.2...1.7.0) --- updated-dependencies: - dependency-name: indexmap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-30 08:01:46 -07:00
indexmap = { version = "1.7", default-features = false }
Add hints to port conflict and lock file panics (#1535) * add hint for port error * add issue filter for port panic * add lock file hint * add metrics endpoint port conflict hint * add hint for tracing endpoint port conflict * add acceptance test for resource conflics * Split out common conflict test code into a function * Add state, metrics, and tracing conflict tests * Add a full set of stderr acceptance test functions This change makes the stdout and stderr acceptance test interfaces identical. * move Zcash listener opening * add todo about hint for disk full * add constant for lock file * match path in state cache * don't match windows cache path * Use Display for state path logs Avoids weird escaping on Windows when using Debug * Add Windows conflict error messages * Turn PORT_IN_USE_ERROR into a regex And add another alternative Windows-specific port error Co-authored-by: teor <teor@riseup.net> Co-authored-by: Jane Lusby <jane@zfnd.org>
2021-01-29 04:36:33 -08:00
lazy_static = "1.4.0"
Upgrade to pin_project 1.0.7 to resolve nightly warnings Except for tower-fallback, which has code that is incompatible with pin_project 1.0.
2021-06-20 17:46:40 -07:00
pin-project = "1.0.7"
Merge pull request #1713 from ZcashFoundation/use-groth16-batch-math Use batch optimizations, load params in groth16::Verifier, verify Spend & Output descriptions in transaction verifier
2021-03-24 09:28:25 -07:00
rand = "0.8"
Add hints to port conflict and lock file panics (#1535) * add hint for port error * add issue filter for port panic * add lock file hint * add metrics endpoint port conflict hint * add hint for tracing endpoint port conflict * add acceptance test for resource conflics * Split out common conflict test code into a function * Add state, metrics, and tracing conflict tests * Add a full set of stderr acceptance test functions This change makes the stdout and stderr acceptance test interfaces identical. * move Zcash listener opening * add todo about hint for disk full * add constant for lock file * match path in state cache * don't match windows cache path * Use Display for state path logs Avoids weird escaping on Windows when using Debug * Add Windows conflict error messages * Turn PORT_IN_USE_ERROR into a regex And add another alternative Windows-specific port error Co-authored-by: teor <teor@riseup.net> Co-authored-by: Jane Lusby <jane@zfnd.org>
2021-01-29 04:36:33 -08:00
regex = "1"
Implement custom Debug for Magic types Related to #63
2019-10-15 16:38:44 -07:00
serde = { version = "1", features = ["serde_derive"] }
Fix merge artifacts in Cargo.toml
2019-10-16 22:56:25 -07:00
thiserror = "1"
Move all git dependencies to published crates. (#58) The earlier issues with version resolution incompatibilities are now resolved, and all the upstream changes we made to tracing are released.
2019-10-08 21:10:01 -07:00
feature: Use the Heartwood protocol version in zebra-network
2020-07-21 01:41:18 -07:00
futures = "0.3"
Upgrade to tokio 0.3.6 from crates.io And remove the tokio git dependency patch
2021-01-11 22:07:15 -08:00
tokio = { version = "0.3.6", features = ["net", "time", "stream", "tracing", "macros", "rt-multi-thread"] }
deps: move to tokio 0.3, tower 0.4 This change is mostly mechanical, with the exception of the changes to the `tower-batch` middleware. This middleware was adapted from `tower::buffer`, and the `tower::buffer` code was changed to implement its own bounded queue, because Tokio 0.3 removed the `mpsc::Sender::poll_send` method. See https://github.com/tower-rs/tower/commit/ddc64e8d4d4d499adef569e284f317288edd6513 for more context on the Tower changes. To match Tower as closely as possible in order to be able to upstream `tower-batch`, those changes are copied from `tower::Buffer` to `tower-batch`.
2020-11-19 11:54:20 -08:00
tokio-util = { version = "0.5", features = ["codec"] }
tower = { version = "0.4", features = ["retry", "discover", "load", "load-shed", "timeout", "util", "buffer"] }
Initial tower-based peer implementation. (#17) Add a tower-based peer implementation. Tower provides middleware for request-response oriented protocols, while Bitcoin/Zcash just send messages which could be interpreted either as requests or responses, depending on context. To bridge this mismatch we define our own internal request/response protocol, and implement a per-peer event loop that scans incoming messages and interprets them either as requests from the remote peer to our node, or as responses to requests we made previously. This is performed by the `PeerService` task, and a corresponding `PeerClient: tower::Service` can send it requests. These tasks are themselves created by a `PeerConnector: tower::Service` which dials a remote peer and performs a handshake.
2019-10-07 15:36:16 -07:00
Deduplicate metrics dependencies (#1561) ## Motivation This PR is motivated by the regression identified in https://github.com/ZcashFoundation/zebra/issues/1349. That PR notes that the metrics stopped working for most of the crates other than `zebrad`. ## Solution This PR resolves the regression by deduplicating the `metrics` crate dependency. During a recent change we upgraded the metrics version in `zebrad` and a couple other of our crates, but we never updated the dependencies in `zebra-state`, `zebra-consensus`, or `zebra-network`. This caused the metrics macros to attempt to retrieve the current metrics exporter through the wrong function. We would install the metrics exporter in `0.13`, but then attempt to look it up through the `0.12` crate, which contains a different instance of the metrics exporter static variable which is unset. Doing this causes the metrics macros to return `None` for the current exporter after which they just silently give up. ## Related Issues closes https://github.com/ZcashFoundation/zebra/issues/1349 ## Follow Up Work I noticed we have quite a few duplicate dependencies in our tree. We might be able to save some compilation time by auditing those and deduplicating them as much as possible. - https://github.com/ZcashFoundation/zebra/issues/1582 Co-authored-by: teor <teor@riseup.net>
2021-01-11 18:28:56 -08:00
metrics = "0.13.0-alpha.8"
feature: Use the Heartwood protocol version in zebra-network
2020-07-21 01:41:18 -07:00
tracing = "0.1"
tracing-futures = "0.2"
tracing-error = { version = "0.1.2", features = ["traced-error"] }
Metrics MVP: add two metrics and export them to Prometheus. Co-authored-by: Deirdre Connolly <deirdre@zfnd.org>
2020-02-14 13:38:33 -08:00
Initial tower-based peer implementation. (#17) Add a tower-based peer implementation. Tower provides middleware for request-response oriented protocols, while Bitcoin/Zcash just send messages which could be interpreted either as requests or responses, depending on context. To bridge this mismatch we define our own internal request/response protocol, and implement a per-peer event loop that scans incoming messages and interprets them either as requests from the remote peer to our node, or as responses to requests we made previously. This is performed by the `PeerService` task, and a corresponding `PeerClient: tower::Service` can send it requests. These tasks are themselves created by a `PeerConnector: tower::Service` which dials a remote peer and performs a handshake.
2019-10-07 15:36:16 -07:00
zebra-chain = { path = "../zebra-chain" }
feature: Use the Heartwood protocol version in zebra-network
2020-07-21 01:41:18 -07:00
[dev-dependencies]
proptest = "0.10"
Add InventoryHash and MetaAddr proptests (#1985) * Make proptest dependencies consistent between chain and network * Implement Arbitrary for InventoryHash and use it in tests * Impl Arbitrary for MetaAddr and use it in tests Also test some extreme times in MetaAddr sanitization.
2021-04-07 10:13:52 -07:00
proptest-derive = "0.3"
Rate limit `GetAddr` messages to any peer, Credit: Equilibrium (#2254) * Rename field to `wait_next_handshake` Make the name a bit more clear regarding to the field's purpose. * Move `MIN_PEER_CONNECTION_INTERVAL` to `constants` Move it to the `constants` module so that it is placed closer to other constants for consistency and to make it easier to see any relationships when changing them. * Rate limit calls to `CandidateSet::update()` This effectively rate limits requests asking for more peer addresses sent to the same peer. A new `min_next_crawl` field was added to `CandidateSet`, and `update` only sends requests for more peer addresses if the call happens after the instant specified by that field. After sending the requests, the field value is updated so that there is a `MIN_PEER_GET_ADDR_INTERVAL` wait time until the next `update` call sends requests again. * Include `update_initial` in rate limiting Move the rate limiting code from `update` to `update_timeout`, so that both `update` and `update_initial` get rate limited. * Test `CandidateSet::update` rate limiting Create a `CandidateSet` that uses a mocked `PeerService`. The mocked service always returns an empty list of peers, but it also checks that the requests only happen after expected instants, determined by the fanout amount and the rate limiting interval. * Refactor to create a `mock_peer_service` helper Move the code from the test to a utility function so that another test will be able to use it as well. * Check number of times service was called Use an `AtomicUsize` shared between the service and the test body that the service increments on every call. The test can then verify if the service was called the number of times it expected. * Test calling `update` after `update_initial` The call to `update` should be skipped because the call to `update_initial` should also be considered in the rate limiting. * Mention that call to `update` may be skipped Make it clearer that in this case the rate limiting causes calls to be skipped, and not that there's an internal sleep that happens. Also remove "to the same peers", because it's more general than that. Co-authored-by: teor <teor@riseup.net>
2021-06-08 16:42:45 -07:00
tokio = { version = "0.3.6", features = ["test-util"] }
Use the default port for configured listen addresses with no port (#2043) * Allow use listen address in config without port * update comments * remove not used alias * use Network::default_port * Move tests and use toml instead json * change error message * Make match more readable Co-authored-by: teor <teor@riseup.net>
2021-04-21 16:14:29 -07:00
toml = "0.5"
Limit protocol messages size (#645) * change body msg limit and test case * accept body at the exact limit len * test the edges of the limit value
2020-07-15 02:15:52 -07:00
Derive Arbitrary impls for a bunch of chain and network types (#2179) Enable proptests for internal and external network protocol messages, using times with the correct protocol-specific ranges. (4 or 8 bytes.)
2021-05-24 08:10:07 -07:00
zebra-chain = { path = "../zebra-chain", features = ["proptest-impl"] }
Limit protocol messages size (#645) * change body msg limit and test case * accept body at the exact limit len * test the edges of the limit value
2020-07-15 02:15:52 -07:00
zebra-test = { path = "../zebra-test/" }