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

60 lines
1.7 KiB
TOML
Raw Normal View History

Add initial version of zebra-state (#414) * rename zebra-storage to zebra-state * Setup initial skeleton for zebra-state * add test * Apply suggestions from code review Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> * move shared test vectors to a common crate Co-authored-by: Jane Lusby <jane@zfnd.org> Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca>
2020-06-02 16:16:17 -07:00
[package]
name = "zebra-state"
V1.0.0-beta.0 (#2973) * V1.0.0-beta.0 * Bump version in install.md
2021-10-29 13:21:26 -07:00
version = "1.0.0-beta.0"
Add initial version of zebra-state (#414) * rename zebra-storage to zebra-state * Setup initial skeleton for zebra-state * add test * Apply suggestions from code review Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> * move shared test vectors to a common crate Co-authored-by: Jane Lusby <jane@zfnd.org> Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca>
2020-06-02 16:16:17 -07:00
authors = ["Zcash Foundation <zebra@zfnd.org>"]
license = "MIT OR Apache-2.0"
edition = "2018"
Add `proptest-impl` feature to `zebra-state` (#2529) * Add `proptest-impl` feature to `zebra-state` This prepares the `zebra-state` crate to be able to export some test-specific helper types and functions. * Add `arbitrary` module to `zebra-state` root A separate module to contain the `Prepare` trait, since it's required by some prop-test strategies and therefore can't be in the `tests` module. * Replace usages of `tests::Prepare` Use the same trait but placed in a new module that's accessible based on the feature flag. * Remove old `Prepare` trait It was obsoleted by the new copy in the `arbitrary` module. * Make `StateService` crate-accessible Prepare for it to be accessible in some test modules. * Refactor strategy function import Import the function directly, instead of just its containing module. * Move some strategy functions to `tests::setup` Create a new module for the strategy functions that are only used internally. Co-authored-by: teor <teor@riseup.net>
2021-07-27 17:01:19 -07:00
[features]
Test if the mempool storage is cleared (#2815) * Move mempool tests into `tests::vector` sub-module Make it consistent with other test modules and prepare for adding property tests. * Reorder imports Make it consistent with the general guidelines followed on other modules. * Export `ChainTipBlock` and `ChainTipSender` Allow these types to be used in other crates for testing purposes. * Derive `Arbitrary` for `ChainTipBlock` Make it easy to generate random `ChainTipBlock`s for usage in property tests. * Refactor to move test methods into `tests` module Reduce the repeated test configuration attributes and make it easier to see what is test specific and what is part of the general implementation. * Add a `Mempool::dummy_call` test helper method Performs a dummy call just so that `poll_ready` gets called. * Use `dummy_call` in existing tests Replace the custom dummy requests with the helper method. * Test if the mempool is cleared on chain reset A chain reset should force the mempool storage to be cleared so that transaction verification can restart using the new chain tip. * Test if mempool is cleared on syncer restart If the block synchronizer falls behind and then starts catching up again, the mempool should be disabled and therefore the storage should be cleared.
2021-10-01 07:44:25 -07:00
proptest-impl = ["proptest", "proptest-derive", "zebra-test"]
Add initial version of zebra-state (#414) * rename zebra-storage to zebra-state * Setup initial skeleton for zebra-state * add test * Apply suggestions from code review Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> * move shared test vectors to a common crate Co-authored-by: Jane Lusby <jane@zfnd.org> Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca>
2020-06-02 16:16:17 -07:00
[dependencies]
zebra-chain = { path = "../zebra-chain" }
Make the CheckpointVerifier handle partial restarts (#736) Also put generic bounds on the BlockVerifier struct, so we get better compilation errors.
2020-07-23 18:47:48 -07:00
Bump dirs from 3.0.2 to 4.0.0 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.2 to 4.0.0. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) --- updated-dependencies: - dependency-name: dirs dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-22 16:34:09 -07:00
dirs = "4.0.0"
build(deps): bump hex from 0.4.2 to 0.4.3 Bumps [hex](https://github.com/KokaKiwi/rust-hex) from 0.4.2 to 0.4.3. - [Release notes](https://github.com/KokaKiwi/rust-hex/releases) - [Commits](https://github.com/KokaKiwi/rust-hex/compare/v0.4.2...v0.4.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-04 02:01:44 -08:00
hex = "0.4.3"
Make the CheckpointVerifier handle partial restarts (#736) Also put generic bounds on the BlockVerifier struct, so we get better compilation errors.
2020-07-23 18:47:48 -07:00
lazy_static = "1.4.0"
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 initial persistent state backend based on `sled` (#473)
2020-06-15 14:41:26 -07:00
serde = { version = "1", features = ["serde_derive"] }
Track anchors and note commitment trees in zebra-state (#2458) * Tidy chain Cargo.toml * Organize imports * Add method to get note commitments from all Actions in Orchard shielded data * Add method to get note commitments from all JoinSplits in Sprout JoinSplitData * Add Request and Response variants for awaiting anchors * Add anchors and note commitment trees to finalized state db * Add (From|Into)Disk impls for tree::Roots and stubs for NoteCommitmentTrees * Track anchors and note commitment trees in Chain Append note commitments to their trees when doing update_chain_state_with, then use the resulting Sapling and Orchard roots to pass to history_tree, and add new roots to the anchor sets. * Handle errors when appending to note commitment trees * Add comments explaining why note commitment are not removed from the tree in revert_chain_state_with * Implementing note commitments in finalized state * Finish serialization of Orchard tree; remove old tree when updating finalize state * Add serialization and finalized state updates for Sprout and Sapling trees * Partially handle trees in non-finalized state. Use Option for trees in Chain * Rebuild trees when forking; change finalized state tree getters to not require height * Pass empty trees to tests; use empty trees by default in Chain * Also rebuild anchor sets when forking * Use empty tree as default in finalized state tree getters (for now) * Use HashMultiSet for anchors in order to make pop_root() work correctly * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS even more * Apply suggestions from code review * Add comments about order of note commitments and related methods/fields * Don't use Option for trees * Set DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES=1 and restore MAX_PARTIAL_CHAIN_BLOCKS * Remove unneeded anchor set rebuilding in fork() * Improve proptest formatting * Add missing comparisons to eq_internal_state * Renamed sprout::tree::NoteCommitmentTree::hash() to root() * Improve comments * Add asserts, add issues to TODOs * Remove impl Default for Chain since it was only used by tests * Improve documentation and assertions; add tree serialization tests * Remove Sprout code, which will be moved to another branch * Add todo! in Sprout tree append() * Remove stub request, response *Anchor* handling for now * Add test for validating Sapling note commitment tree using test blocks * Increase database version (new columns added for note commitment trees and anchors) * Update test to make sure the order of sapling_note_commitments() is being tested * Improve comments and structure of the test * Improve variable names again * Rustfmt Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> Co-authored-by: Conrado P. L. Gouvea <conradoplg@gmail.com> Co-authored-by: Conrado Gouvea <conrado@zfnd.org> Co-authored-by: teor <teor@riseup.net>
2021-07-29 06:37:18 -07:00
bincode = "1"
Make the CheckpointVerifier handle partial restarts (#736) Also put generic bounds on the BlockVerifier struct, so we get better compilation errors.
2020-07-23 18:47:48 -07:00
Bump futures from 0.3.15 to 0.3.17 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.15 to 0.3.17. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.15...0.3.17) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-31 12:21:00 -07:00
futures = "0.3.17"
Update to Tokio 1.13.0 (#2994) * Update `tower` to version `0.4.9` Update to latest version to add support for Tokio version 1. * Replace usage of `ServiceExt::ready_and` It was deprecated in favor of `ServiceExt::ready`. * Update Tokio dependency to version `1.13.0` This will break the build because the code isn't ready for the update, but future commits will fix the issues. * Replace import of `tokio::stream::StreamExt` Use `futures::stream::StreamExt` instead, because newer versions of Tokio don't have the `stream` feature. * Use `IntervalStream` in `zebra-network` In newer versions of Tokio `Interval` doesn't implement `Stream`, so the wrapper types from `tokio-stream` have to be used instead. * Use `IntervalStream` in `inventory_registry` In newer versions of Tokio the `Interval` type doesn't implement `Stream`, so `tokio_stream::wrappers::IntervalStream` has to be used instead. * Use `BroadcastStream` in `inventory_registry` In newer versions of Tokio `broadcast::Receiver` doesn't implement `Stream`, so `tokio_stream::wrappers::BroadcastStream` instead. This also requires changing the error type that is used. * Handle `Semaphore::acquire` error in `tower-batch` Newer versions of Tokio can return an error if the semaphore is closed. This shouldn't happen in `tower-batch` because the semaphore is never closed. * Handle `Semaphore::acquire` error in `zebrad` test On newer versions of Tokio `Semaphore::acquire` can return an error if the semaphore is closed. This shouldn't happen in the test because the semaphore is never closed. * Update some `zebra-network` dependencies Use versions compatible with Tokio version 1. * Upgrade Hyper to version 0.14 Use a version that supports Tokio version 1. * Update `metrics` dependency to version 0.17 And also update the `metrics-exporter-prometheus` to version 0.6.1. These updates are to make sure Tokio 1 is supported. * Use `f64` as the histogram data type `u64` isn't supported as the histogram data type in newer versions of `metrics`. * Update the initialization of the metrics component Make it compatible with the new version of `metrics`. * Simplify build version counter Remove all constants and use the new `metrics::incement_counter!` macro. * Change metrics output line to match on The snapshot string isn't included in the newer version of `metrics-exporter-prometheus`. * Update `sentry` to version 0.23.0 Use a version compatible with Tokio version 1. * Remove usage of `TracingIntegration` This seems to not be available from `sentry-tracing` anymore, so it needs to be replaced. * Add sentry layer to tracing initialization This seems like the replacement for `TracingIntegration`. * Remove unnecessary conversion Suggested by a Clippy lint. * Update Cargo lock file Apply all of the updates to dependencies. * Ban duplicate tokio dependencies Also ban git sources for tokio dependencies. * Stop allowing sentry-tracing git repository in `deny.toml` * Allow remaining duplicates after the tokio upgrade * Use C: drive for CI build output on Windows GitHub Actions uses a Windows image with two disk drives, and the default D: drive is smaller than the C: drive. Zebra currently uses a lot of space to build, so it has to use the C: drive to avoid CI build failures because of insufficient space. Co-authored-by: teor <teor@riseup.net>
2021-11-02 11:46:57 -07:00
metrics = "0.17.0"
tower = { version = "0.4.9", features = ["buffer", "util"] }
Improve tracing output in chain verifier
2020-07-22 11:54:52 -07:00
tracing = "0.1"
Bump thiserror from 1.0.29 to 1.0.30 (#2856) Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.29 to 1.0.30. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.29...1.0.30) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Deirdre Connolly <deirdre@zfnd.org>
2021-10-11 13:36:44 -07:00
thiserror = "1.0.30"
Update to Tokio 1.13.0 (#2994) * Update `tower` to version `0.4.9` Update to latest version to add support for Tokio version 1. * Replace usage of `ServiceExt::ready_and` It was deprecated in favor of `ServiceExt::ready`. * Update Tokio dependency to version `1.13.0` This will break the build because the code isn't ready for the update, but future commits will fix the issues. * Replace import of `tokio::stream::StreamExt` Use `futures::stream::StreamExt` instead, because newer versions of Tokio don't have the `stream` feature. * Use `IntervalStream` in `zebra-network` In newer versions of Tokio `Interval` doesn't implement `Stream`, so the wrapper types from `tokio-stream` have to be used instead. * Use `IntervalStream` in `inventory_registry` In newer versions of Tokio the `Interval` type doesn't implement `Stream`, so `tokio_stream::wrappers::IntervalStream` has to be used instead. * Use `BroadcastStream` in `inventory_registry` In newer versions of Tokio `broadcast::Receiver` doesn't implement `Stream`, so `tokio_stream::wrappers::BroadcastStream` instead. This also requires changing the error type that is used. * Handle `Semaphore::acquire` error in `tower-batch` Newer versions of Tokio can return an error if the semaphore is closed. This shouldn't happen in `tower-batch` because the semaphore is never closed. * Handle `Semaphore::acquire` error in `zebrad` test On newer versions of Tokio `Semaphore::acquire` can return an error if the semaphore is closed. This shouldn't happen in the test because the semaphore is never closed. * Update some `zebra-network` dependencies Use versions compatible with Tokio version 1. * Upgrade Hyper to version 0.14 Use a version that supports Tokio version 1. * Update `metrics` dependency to version 0.17 And also update the `metrics-exporter-prometheus` to version 0.6.1. These updates are to make sure Tokio 1 is supported. * Use `f64` as the histogram data type `u64` isn't supported as the histogram data type in newer versions of `metrics`. * Update the initialization of the metrics component Make it compatible with the new version of `metrics`. * Simplify build version counter Remove all constants and use the new `metrics::incement_counter!` macro. * Change metrics output line to match on The snapshot string isn't included in the newer version of `metrics-exporter-prometheus`. * Update `sentry` to version 0.23.0 Use a version compatible with Tokio version 1. * Remove usage of `TracingIntegration` This seems to not be available from `sentry-tracing` anymore, so it needs to be replaced. * Add sentry layer to tracing initialization This seems like the replacement for `TracingIntegration`. * Remove unnecessary conversion Suggested by a Clippy lint. * Update Cargo lock file Apply all of the updates to dependencies. * Ban duplicate tokio dependencies Also ban git sources for tokio dependencies. * Stop allowing sentry-tracing git repository in `deny.toml` * Allow remaining duplicates after the tokio upgrade * Use C: drive for CI build output on Windows GitHub Actions uses a Windows image with two disk drives, and the default D: drive is smaller than the C: drive. Zebra currently uses a lot of space to build, so it has to use the C: drive to avoid CI build failures because of insufficient space. Co-authored-by: teor <teor@riseup.net>
2021-11-02 11:46:57 -07:00
tokio = { version = "1.13.0", features = ["sync"] }
build(deps): bump displaydoc from 0.2.1 to 0.2.2 (#2439) Bumps [displaydoc](https://github.com/yaahc/displaydoc) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/yaahc/displaydoc/releases) - [Changelog](https://github.com/yaahc/displaydoc/blob/master/CHANGELOG.md) - [Commits](https://github.com/yaahc/displaydoc/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: displaydoc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-07-02 10:20:47 -07:00
displaydoc = "0.2.2"
Update dependencies to support Apple M1, fix Windows CI LLVM paths (#2026) * build(deps): update for Apple M1 * fix ci * bump rocksdb * bump zcash_script
2021-04-19 03:39:24 -07:00
rocksdb = "0.16.0"
Stop using /dev/shm on Linux (#1338) Some systems have a very small /dev/shm, for example, see: https://github.com/docker-library/postgres/issues/416 So we should just use the temporary directory on all operating systems. Also: * use TempDir to generate the temporary path * delete the code that we copied from sled * prefix the temporary path with the state version and network
2020-11-19 19:01:19 -08:00
tempdir = "0.3.7"
Implement AdjustedDifficulty creation Also: * call the difficulty check from `block_is_contextually_valid` * add a stub `difficulty_threshold_is_valid` function
2020-11-22 17:56:38 -08:00
chrono = "0.4.19"
build(deps): bump rlimit from 0.5.3 to 0.5.4 Bumps [rlimit](https://github.com/Nugine/rlimit) from 0.5.3 to 0.5.4. - [Release notes](https://github.com/Nugine/rlimit/releases) - [Commits](https://github.com/Nugine/rlimit/compare/v0.5.3...v0.5.4) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-01 02:01:27 -08:00
rlimit = "0.5.4"
Track anchors and note commitment trees in zebra-state (#2458) * Tidy chain Cargo.toml * Organize imports * Add method to get note commitments from all Actions in Orchard shielded data * Add method to get note commitments from all JoinSplits in Sprout JoinSplitData * Add Request and Response variants for awaiting anchors * Add anchors and note commitment trees to finalized state db * Add (From|Into)Disk impls for tree::Roots and stubs for NoteCommitmentTrees * Track anchors and note commitment trees in Chain Append note commitments to their trees when doing update_chain_state_with, then use the resulting Sapling and Orchard roots to pass to history_tree, and add new roots to the anchor sets. * Handle errors when appending to note commitment trees * Add comments explaining why note commitment are not removed from the tree in revert_chain_state_with * Implementing note commitments in finalized state * Finish serialization of Orchard tree; remove old tree when updating finalize state * Add serialization and finalized state updates for Sprout and Sapling trees * Partially handle trees in non-finalized state. Use Option for trees in Chain * Rebuild trees when forking; change finalized state tree getters to not require height * Pass empty trees to tests; use empty trees by default in Chain * Also rebuild anchor sets when forking * Use empty tree as default in finalized state tree getters (for now) * Use HashMultiSet for anchors in order to make pop_root() work correctly * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS even more * Apply suggestions from code review * Add comments about order of note commitments and related methods/fields * Don't use Option for trees * Set DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES=1 and restore MAX_PARTIAL_CHAIN_BLOCKS * Remove unneeded anchor set rebuilding in fork() * Improve proptest formatting * Add missing comparisons to eq_internal_state * Renamed sprout::tree::NoteCommitmentTree::hash() to root() * Improve comments * Add asserts, add issues to TODOs * Remove impl Default for Chain since it was only used by tests * Improve documentation and assertions; add tree serialization tests * Remove Sprout code, which will be moved to another branch * Add todo! in Sprout tree append() * Remove stub request, response *Anchor* handling for now * Add test for validating Sapling note commitment tree using test blocks * Increase database version (new columns added for note commitment trees and anchors) * Update test to make sure the order of sapling_note_commitments() is being tested * Improve comments and structure of the test * Improve variable names again * Rustfmt Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> Co-authored-by: Conrado P. L. Gouvea <conradoplg@gmail.com> Co-authored-by: Conrado Gouvea <conrado@zfnd.org> Co-authored-by: teor <teor@riseup.net>
2021-07-29 06:37:18 -07:00
# TODO: this crate is not maintained anymore. Replace it?
# https://github.com/ZcashFoundation/zebra/issues/2523
Depend on a multiset git commit that includes a bug fix (#3033) This fixes a bug in MultiSet::remove_all: https://github.com/jmitchell/multiset/pull/21
2021-11-11 13:37:01 -08:00
#
# Pinned to a commit which includes bug fix https://github.com/jmitchell/multiset/pull/21
# The fix should be included in multiset 0.0.6.
multiset = { git = "https://github.com/jmitchell/multiset", rev = "91ef8550b518f75ae87ae0d8771150f259fd34d5" }
Add initial version of zebra-state (#414) * rename zebra-storage to zebra-state * Setup initial skeleton for zebra-state * add test * Apply suggestions from code review Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> * move shared test vectors to a common crate Co-authored-by: Jane Lusby <jane@zfnd.org> Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca>
2020-06-02 16:16:17 -07:00
Add `proptest-impl` feature to `zebra-state` (#2529) * Add `proptest-impl` feature to `zebra-state` This prepares the `zebra-state` crate to be able to export some test-specific helper types and functions. * Add `arbitrary` module to `zebra-state` root A separate module to contain the `Prepare` trait, since it's required by some prop-test strategies and therefore can't be in the `tests` module. * Replace usages of `tests::Prepare` Use the same trait but placed in a new module that's accessible based on the feature flag. * Remove old `Prepare` trait It was obsoleted by the new copy in the `arbitrary` module. * Make `StateService` crate-accessible Prepare for it to be accessible in some test modules. * Refactor strategy function import Import the function directly, instead of just its containing module. * Move some strategy functions to `tests::setup` Create a new module for the strategy functions that are only used internally. Co-authored-by: teor <teor@riseup.net>
2021-07-27 17:01:19 -07:00
proptest = { version = "0.10.1", optional = true }
Test if the mempool storage is cleared (#2815) * Move mempool tests into `tests::vector` sub-module Make it consistent with other test modules and prepare for adding property tests. * Reorder imports Make it consistent with the general guidelines followed on other modules. * Export `ChainTipBlock` and `ChainTipSender` Allow these types to be used in other crates for testing purposes. * Derive `Arbitrary` for `ChainTipBlock` Make it easy to generate random `ChainTipBlock`s for usage in property tests. * Refactor to move test methods into `tests` module Reduce the repeated test configuration attributes and make it easier to see what is test specific and what is part of the general implementation. * Add a `Mempool::dummy_call` test helper method Performs a dummy call just so that `poll_ready` gets called. * Use `dummy_call` in existing tests Replace the custom dummy requests with the helper method. * Test if the mempool is cleared on chain reset A chain reset should force the mempool storage to be cleared so that transaction verification can restart using the new chain tip. * Test if mempool is cleared on syncer restart If the block synchronizer falls behind and then starts catching up again, the mempool should be disabled and therefore the storage should be cleared.
2021-10-01 07:44:25 -07:00
proptest-derive = { version = "0.3", optional = true }
Add `proptest-impl` feature to `zebra-state` (#2529) * Add `proptest-impl` feature to `zebra-state` This prepares the `zebra-state` crate to be able to export some test-specific helper types and functions. * Add `arbitrary` module to `zebra-state` root A separate module to contain the `Prepare` trait, since it's required by some prop-test strategies and therefore can't be in the `tests` module. * Replace usages of `tests::Prepare` Use the same trait but placed in a new module that's accessible based on the feature flag. * Remove old `Prepare` trait It was obsoleted by the new copy in the `arbitrary` module. * Make `StateService` crate-accessible Prepare for it to be accessible in some test modules. * Refactor strategy function import Import the function directly, instead of just its containing module. * Move some strategy functions to `tests::setup` Create a new module for the strategy functions that are only used internally. Co-authored-by: teor <teor@riseup.net>
2021-07-27 17:01:19 -07:00
zebra-test = { path = "../zebra-test/", optional = true }
Add initial version of zebra-state (#414) * rename zebra-storage to zebra-state * Setup initial skeleton for zebra-state * add test * Apply suggestions from code review Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> * move shared test vectors to a common crate Co-authored-by: Jane Lusby <jane@zfnd.org> Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca>
2020-06-02 16:16:17 -07:00
[dev-dependencies]
export proptest impls for use in downstream crates (#1092) * export proptest impls for use in downstream crates * add testjob for disabled feature in zebra-chain * run rustfmt * try to fix github actions syntax * differentiate name * prove that github action tests zebra-chain build without features * revert change from last commit now that test is running * remove accidentally introduced newline * Update .github/workflows/ci.yml Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> Co-authored-by: Deirdre Connolly <deirdre@zfnd.org>
2020-09-23 18:52:52 -07:00
zebra-chain = { path = "../zebra-chain", features = ["proptest-impl"] }
consolidate test init functions into zebra-test (#541) * consolidate test init logic into one place * rustfmt Co-authored-by: Jane Lusby <jane@zfnd.org>
2020-06-24 11:30:20 -07:00
zebra-test = { path = "../zebra-test/" }
Make the CheckpointVerifier handle partial restarts (#736) Also put generic bounds on the BlockVerifier struct, so we get better compilation errors.
2020-07-23 18:47:48 -07:00
build(deps): bump color-eyre from 0.5.10 to 0.5.11 Bumps [color-eyre](https://github.com/yaahc/color-eyre) from 0.5.10 to 0.5.11. - [Release notes](https://github.com/yaahc/color-eyre/releases) - [Changelog](https://github.com/yaahc/color-eyre/blob/v0.5.11/CHANGELOG.md) - [Commits](https://github.com/yaahc/color-eyre/compare/v0.5.10...v0.5.11) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-14 02:02:13 -07:00
color-eyre = "0.5.11"
build(deps): bump once_cell from 1.7.2 to 1.8.0 Bumps [once_cell](https://github.com/matklad/once_cell) from 1.7.2 to 1.8.0. - [Release notes](https://github.com/matklad/once_cell/releases) - [Changelog](https://github.com/matklad/once_cell/blob/master/CHANGELOG.md) - [Commits](https://github.com/matklad/once_cell/compare/v1.7.2...v1.8.0) --- updated-dependencies: - dependency-name: once_cell dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-14 02:01:34 -07:00
once_cell = "1.8"
Reject duplicate sprout nullifiers in the state (#2477) * Reject duplicate sprout nullifiers in the state * Improve docs and error messages * Clarify "must be present" assert logs * Move nullifier checks to their own module Also: * make non-finalized nullifier checks and errors generic over sprout, sapling, and orchard * create and update module and function documentation * Fix a block type name in docs * Move state assertions or skip them during tests These changes enable state testing, while still asserting in production. * Add sprout duplicate nullifier tests * Improve comments * Set value balance to 0 to pass future chain value pool checks * Test finalized state in sprout nullifier accept test * Replace assert with expect * Improve assertion messages
2021-07-14 05:06:43 -07:00
itertools = "0.10.1"
fix spandoc instrumentation for await expressions (#618) * fix spandoc instrumentation for await expressions * depend on released version of spandoc
2020-07-09 14:43:44 -07:00
spandoc = "0.2"
implement initial persistent state backend based on `sled` (#473)
2020-06-15 14:41:26 -07:00
tempdir = "0.3.7"
Update to Tokio 1.13.0 (#2994) * Update `tower` to version `0.4.9` Update to latest version to add support for Tokio version 1. * Replace usage of `ServiceExt::ready_and` It was deprecated in favor of `ServiceExt::ready`. * Update Tokio dependency to version `1.13.0` This will break the build because the code isn't ready for the update, but future commits will fix the issues. * Replace import of `tokio::stream::StreamExt` Use `futures::stream::StreamExt` instead, because newer versions of Tokio don't have the `stream` feature. * Use `IntervalStream` in `zebra-network` In newer versions of Tokio `Interval` doesn't implement `Stream`, so the wrapper types from `tokio-stream` have to be used instead. * Use `IntervalStream` in `inventory_registry` In newer versions of Tokio the `Interval` type doesn't implement `Stream`, so `tokio_stream::wrappers::IntervalStream` has to be used instead. * Use `BroadcastStream` in `inventory_registry` In newer versions of Tokio `broadcast::Receiver` doesn't implement `Stream`, so `tokio_stream::wrappers::BroadcastStream` instead. This also requires changing the error type that is used. * Handle `Semaphore::acquire` error in `tower-batch` Newer versions of Tokio can return an error if the semaphore is closed. This shouldn't happen in `tower-batch` because the semaphore is never closed. * Handle `Semaphore::acquire` error in `zebrad` test On newer versions of Tokio `Semaphore::acquire` can return an error if the semaphore is closed. This shouldn't happen in the test because the semaphore is never closed. * Update some `zebra-network` dependencies Use versions compatible with Tokio version 1. * Upgrade Hyper to version 0.14 Use a version that supports Tokio version 1. * Update `metrics` dependency to version 0.17 And also update the `metrics-exporter-prometheus` to version 0.6.1. These updates are to make sure Tokio 1 is supported. * Use `f64` as the histogram data type `u64` isn't supported as the histogram data type in newer versions of `metrics`. * Update the initialization of the metrics component Make it compatible with the new version of `metrics`. * Simplify build version counter Remove all constants and use the new `metrics::incement_counter!` macro. * Change metrics output line to match on The snapshot string isn't included in the newer version of `metrics-exporter-prometheus`. * Update `sentry` to version 0.23.0 Use a version compatible with Tokio version 1. * Remove usage of `TracingIntegration` This seems to not be available from `sentry-tracing` anymore, so it needs to be replaced. * Add sentry layer to tracing initialization This seems like the replacement for `TracingIntegration`. * Remove unnecessary conversion Suggested by a Clippy lint. * Update Cargo lock file Apply all of the updates to dependencies. * Ban duplicate tokio dependencies Also ban git sources for tokio dependencies. * Stop allowing sentry-tracing git repository in `deny.toml` * Allow remaining duplicates after the tokio upgrade * Use C: drive for CI build output on Windows GitHub Actions uses a Windows image with two disk drives, and the default D: drive is smaller than the C: drive. Zebra currently uses a lot of space to build, so it has to use the C: drive to avoid CI build failures because of insufficient space. Co-authored-by: teor <teor@riseup.net>
2021-11-02 11:46:57 -07:00
tokio = { version = "1.13.0", features = ["full"] }
Track anchors and note commitment trees in zebra-state (#2458) * Tidy chain Cargo.toml * Organize imports * Add method to get note commitments from all Actions in Orchard shielded data * Add method to get note commitments from all JoinSplits in Sprout JoinSplitData * Add Request and Response variants for awaiting anchors * Add anchors and note commitment trees to finalized state db * Add (From|Into)Disk impls for tree::Roots and stubs for NoteCommitmentTrees * Track anchors and note commitment trees in Chain Append note commitments to their trees when doing update_chain_state_with, then use the resulting Sapling and Orchard roots to pass to history_tree, and add new roots to the anchor sets. * Handle errors when appending to note commitment trees * Add comments explaining why note commitment are not removed from the tree in revert_chain_state_with * Implementing note commitments in finalized state * Finish serialization of Orchard tree; remove old tree when updating finalize state * Add serialization and finalized state updates for Sprout and Sapling trees * Partially handle trees in non-finalized state. Use Option for trees in Chain * Rebuild trees when forking; change finalized state tree getters to not require height * Pass empty trees to tests; use empty trees by default in Chain * Also rebuild anchor sets when forking * Use empty tree as default in finalized state tree getters (for now) * Use HashMultiSet for anchors in order to make pop_root() work correctly * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS even more * Apply suggestions from code review * Add comments about order of note commitments and related methods/fields * Don't use Option for trees * Set DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES=1 and restore MAX_PARTIAL_CHAIN_BLOCKS * Remove unneeded anchor set rebuilding in fork() * Improve proptest formatting * Add missing comparisons to eq_internal_state * Renamed sprout::tree::NoteCommitmentTree::hash() to root() * Improve comments * Add asserts, add issues to TODOs * Remove impl Default for Chain since it was only used by tests * Improve documentation and assertions; add tree serialization tests * Remove Sprout code, which will be moved to another branch * Add todo! in Sprout tree append() * Remove stub request, response *Anchor* handling for now * Add test for validating Sapling note commitment tree using test blocks * Increase database version (new columns added for note commitment trees and anchors) * Update test to make sure the order of sapling_note_commitments() is being tested * Improve comments and structure of the test * Improve variable names again * Rustfmt Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> Co-authored-by: Conrado P. L. Gouvea <conradoplg@gmail.com> Co-authored-by: Conrado Gouvea <conrado@zfnd.org> Co-authored-by: teor <teor@riseup.net>
2021-07-29 06:37:18 -07:00
# TODO: replace w/ crate version when released: https://github.com/ZcashFoundation/zebra/issues/2083
# Note: if updating this, also update the workspace Cargo.toml to match.
Update shared NU5 dependencies, set the NU5 testnet activation network upgrade parameters (#2825) * Check return value of zcash_script_new_precomputed_tx * Set the NU5 testnet activation height to 1_590_000 * Apply suggestions from code review Co-authored-by: teor <teor@riseup.net> * Update Nu5 constants to new values * Update ZIP-244 test vectors for new branch ID * Squashed commit of the following: commit bdb120a249e3e889a913114a712505defdade1d4 Author: Deirdre Connolly <durumcrustulum@gmail.com> Date: Tue Oct 5 11:54:01 2021 -0400 Use pallas::Base::from_str_vartime() in sinsemilla tests commit e99fa4925857840fa65ccfb4a076ec412e416576 Author: Deirdre Connolly <durumcrustulum@gmail.com> Date: Tue Oct 5 11:45:24 2021 -0400 Compiles commit a5200181146bfd2aa1e09abea2caaa7a7ceb006e Author: Deirdre Connolly <durumcrustulum@gmail.com> Date: Tue Oct 5 10:15:17 2021 -0400 Incomplete upgrade of deps * Squashed commit of the following: commit 8d1b76ec5626517817c3a4d9f3950acc90a359df Author: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com> Date: Tue Oct 5 04:02:26 2021 +0000 Update `zcash_script` to support V5 transactions Use a newer version of `zcash_script` that has been updated to support V5 transactions. commit 371233628ae61e0c25d6ba8f31d9dba42823becb Author: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com> Date: Tue Oct 5 03:06:20 2021 +0000 Update Zcash dependencies Update some Zcash crates: - `halo2` - `incrementalmerkletree' (patch version) - `orchard` (patch version) - `zcash_history` (patch version) - `zcash_note_encryption` (patch version) - `zcash_primitives` (patch version) And also update the `group` dependency so that the code remains compatible. commit de5cf1ec40c3fc08670fc971cdf3e65e13d9f4c7 Author: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com> Date: Tue Oct 5 03:04:13 2021 +0000 Update error message assertion Use the updated message for the expected error variant. * Update `zcash_script` to support V5 transactions Use a newer version of `zcash_script` that has been updated to support V5 transactions. Co-authored-by: Conrado Gouvea <conrado@zfnd.org> Co-authored-by: teor <teor@riseup.net>
2021-10-05 18:08:41 -07:00
halo2 = "=0.1.0-beta.1"
Track anchors and note commitment trees in zebra-state (#2458) * Tidy chain Cargo.toml * Organize imports * Add method to get note commitments from all Actions in Orchard shielded data * Add method to get note commitments from all JoinSplits in Sprout JoinSplitData * Add Request and Response variants for awaiting anchors * Add anchors and note commitment trees to finalized state db * Add (From|Into)Disk impls for tree::Roots and stubs for NoteCommitmentTrees * Track anchors and note commitment trees in Chain Append note commitments to their trees when doing update_chain_state_with, then use the resulting Sapling and Orchard roots to pass to history_tree, and add new roots to the anchor sets. * Handle errors when appending to note commitment trees * Add comments explaining why note commitment are not removed from the tree in revert_chain_state_with * Implementing note commitments in finalized state * Finish serialization of Orchard tree; remove old tree when updating finalize state * Add serialization and finalized state updates for Sprout and Sapling trees * Partially handle trees in non-finalized state. Use Option for trees in Chain * Rebuild trees when forking; change finalized state tree getters to not require height * Pass empty trees to tests; use empty trees by default in Chain * Also rebuild anchor sets when forking * Use empty tree as default in finalized state tree getters (for now) * Use HashMultiSet for anchors in order to make pop_root() work correctly * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS * Reduce DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES and MAX_PARTIAL_CHAIN_BLOCKS even more * Apply suggestions from code review * Add comments about order of note commitments and related methods/fields * Don't use Option for trees * Set DEFAULT_PARTIAL_CHAIN_PROPTEST_CASES=1 and restore MAX_PARTIAL_CHAIN_BLOCKS * Remove unneeded anchor set rebuilding in fork() * Improve proptest formatting * Add missing comparisons to eq_internal_state * Renamed sprout::tree::NoteCommitmentTree::hash() to root() * Improve comments * Add asserts, add issues to TODOs * Remove impl Default for Chain since it was only used by tests * Improve documentation and assertions; add tree serialization tests * Remove Sprout code, which will be moved to another branch * Add todo! in Sprout tree append() * Remove stub request, response *Anchor* handling for now * Add test for validating Sapling note commitment tree using test blocks * Increase database version (new columns added for note commitment trees and anchors) * Update test to make sure the order of sapling_note_commitments() is being tested * Improve comments and structure of the test * Improve variable names again * Rustfmt Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> Co-authored-by: Conrado P. L. Gouvea <conradoplg@gmail.com> Co-authored-by: Conrado Gouvea <conrado@zfnd.org> Co-authored-by: teor <teor@riseup.net>
2021-07-29 06:37:18 -07:00
jubjub = "0.7.0"
Reject duplicate sprout nullifiers in the state (#2477) * Reject duplicate sprout nullifiers in the state * Improve docs and error messages * Clarify "must be present" assert logs * Move nullifier checks to their own module Also: * make non-finalized nullifier checks and errors generic over sprout, sapling, and orchard * create and update module and function documentation * Fix a block type name in docs * Move state assertions or skip them during tests These changes enable state testing, while still asserting in production. * Add sprout duplicate nullifier tests * Improve comments * Set value balance to 0 to pass future chain value pool checks * Test finalized state in sprout nullifier accept test * Replace assert with expect * Improve assertion messages
2021-07-14 05:06:43 -07:00
Add tests for `Chain` implementation (#1093) * Begin work on RFC5 implementation * I think this is necessary * holy shit supertrait implemented via subtrait * implement most of the chain functions * change to slightly better name * implement fork * fix outpoint handling in Chain struct * update expect for work * resolve review comment * split utxo into two sets * update the Chain definition * just a little more * update comment * Apply suggestions from code review Co-authored-by: teor <teor@riseup.net> * apply changes from code review * remove allow attribute in zebra-state/lib.rs * Update zebra-state/src/memory_state.rs Co-authored-by: teor <teor@riseup.net> * merge ChainSet type into MemoryState * rename state impl types * Add error messages to asserts * checkpoint so I can split off arbitrary changes into a PR * export proptest impls for use in downstream crates * add testjob for disabled feature in zebra-chain * run rustfmt * try to fix github actions syntax * differentiate name * prove that github action tests zebra-chain build without features * revert change from last commit now that test is running * remove accidentally introduced newline * checkpoint * add module doc comment * update RFC for utxos * add missing header * working proptest for Chain * apply change from chain impl PR * setup config for proptests * Update zebra-chain/src/block/arbitrary.rs Co-authored-by: teor <teor@riseup.net> * run rustfmt Co-authored-by: teor <teor@riseup.net>
2020-10-02 15:51:51 -07:00
proptest = "0.10.1"
build(deps): bump proptest-derive from 0.2.0 to 0.3.0 Bumps [proptest-derive](https://github.com/AltSysrq/proptest) from 0.2.0 to 0.3.0. - [Release notes](https://github.com/AltSysrq/proptest/releases) - [Changelog](https://github.com/AltSysrq/proptest/blob/master/CHANGELOG.md) - [Commits](https://github.com/AltSysrq/proptest/compare/proptest-derive-0.2.0...proptest-derive-0.3.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-21 17:52:51 -08:00
proptest-derive = "0.3"