2019-08-29 14:46:54 -07:00
|
|
|
[workspace]
|
|
|
|
|
members = [
|
2020-07-14 13:23:43 -07:00
|
|
|
"zebrad",
|
2019-08-29 14:46:54 -07:00
|
|
|
"zebra-chain",
|
|
|
|
|
"zebra-network",
|
2020-06-02 16:16:17 -07:00
|
|
|
"zebra-state",
|
2019-08-29 14:46:54 -07:00
|
|
|
"zebra-script",
|
|
|
|
|
"zebra-consensus",
|
|
|
|
|
"zebra-rpc",
|
|
|
|
|
"zebra-client",
|
2020-06-22 19:34:11 -07:00
|
|
|
"zebra-test",
|
2020-07-10 12:31:01 -07:00
|
|
|
"zebra-utils",
|
2020-07-14 13:23:43 -07:00
|
|
|
"tower-batch",
|
2020-07-14 16:21:01 -07:00
|
|
|
"tower-fallback",
|
2019-10-10 15:43:54 -07:00
|
|
|
]
|
fix panic in seed subcommand (#401)
Co-authored-by: Jane Lusby <jane@zfnd.org>
Prior to this change, the seed subcommand would consistently encounter a panic in one of the background tasks, but would continue running after the panic. This is indicative of two bugs.
First, zebrad was not configured to treat panics as non recoverable and instead defaulted to the tokio defaults, which are to catch panics in tasks and return them via the join handle if available, or to print them if the join handle has been discarded. This is likely a poor fit for zebrad as an application, we do not need to maximize uptime or minimize the extent of an outage should one of our tasks / services start encountering panics. Ignoring a panic increases our risk of observing invalid state, causing all sorts of wild and bad bugs. To deal with this we've switched the default panic behavior from `unwind` to `abort`. This makes panics fail immediately and take down the entire application, regardless of where they occur, which is consistent with our treatment of misbehaving connections.
The second bug is the panic itself. This was triggered by a duplicate entry in the initial_peers set. To fix this we've switched the storage for the peers from a `Vec` to a `HashSet`, which has similar properties but guarantees uniqueness of its keys.
2020-05-27 17:40:12 -07:00
|
|
|
|
|
|
|
|
[profile.dev]
|
|
|
|
|
panic = "abort"
|
|
|
|
|
|
2021-12-14 09:12:35 -08:00
|
|
|
# Speed up tests by optimizing performance-critical crates
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.blake2b_simd]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.ff]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.group]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.pasta_curves]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.halo2]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.bls12_381]
|
|
|
|
|
opt-level = 3
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.minreq]
|
|
|
|
|
opt-level = 1
|
|
|
|
|
|
|
|
|
|
[profile.dev.package.zcash_proofs]
|
|
|
|
|
opt-level = 1
|
|
|
|
|
|
|
|
|
|
|
fix panic in seed subcommand (#401)
Co-authored-by: Jane Lusby <jane@zfnd.org>
Prior to this change, the seed subcommand would consistently encounter a panic in one of the background tasks, but would continue running after the panic. This is indicative of two bugs.
First, zebrad was not configured to treat panics as non recoverable and instead defaulted to the tokio defaults, which are to catch panics in tasks and return them via the join handle if available, or to print them if the join handle has been discarded. This is likely a poor fit for zebrad as an application, we do not need to maximize uptime or minimize the extent of an outage should one of our tasks / services start encountering panics. Ignoring a panic increases our risk of observing invalid state, causing all sorts of wild and bad bugs. To deal with this we've switched the default panic behavior from `unwind` to `abort`. This makes panics fail immediately and take down the entire application, regardless of where they occur, which is consistent with our treatment of misbehaving connections.
The second bug is the panic itself. This was triggered by a duplicate entry in the initial_peers set. To fix this we've switched the storage for the peers from a `Vec` to a `HashSet`, which has similar properties but guarantees uniqueness of its keys.
2020-05-27 17:40:12 -07:00
|
|
|
[profile.release]
|
2020-06-04 19:34:06 -07:00
|
|
|
panic = "abort"
|
2020-09-21 14:00:20 -07:00
|
|
|
|
|
|
|
|
[patch.crates-io]
|
2020-12-13 18:04:52 -08:00
|
|
|
|
2021-11-25 08:26:32 -08:00
|
|
|
# TODO: replace with upstream orchard (#3056)
|
2021-11-16 19:26:15 -08:00
|
|
|
orchard = { git = "https://github.com/ZcashFoundation/orchard.git", rev = "568e24cd5f129158375d7ac7d98c89ebff4f982f" }
|
2021-11-19 15:02:56 -08:00
|
|
|
|
2021-11-25 08:26:32 -08:00
|
|
|
# TODO: replace with upstream librustzcash when these changes are merged (#3037)
|
|
|
|
|
#
|
|
|
|
|
# This zcash_proofs patch doesn't work, maybe because of features?
|
|
|
|
|
#zcash_proofs = { git = "https://github.com/ZcashFoundation/librustzcash.git", rev = "dea8d97d5ed09bdb6673cb64d0a63706f71c2f61" }
|
|
|
|
|
|
|
|
|
|
# Use the ZcashFoundation fork where possible, to avoid duplicate dependencies
|
|
|
|
|
equihash = { git = "https://github.com/ZcashFoundation/librustzcash.git", rev = "dea8d97d5ed09bdb6673cb64d0a63706f71c2f61" }
|
|
|
|
|
zcash_note_encryption = { git = "https://github.com/ZcashFoundation/librustzcash.git", rev = "dea8d97d5ed09bdb6673cb64d0a63706f71c2f61" }
|
|
|
|
|
zcash_primitives = { git = "https://github.com/ZcashFoundation/librustzcash.git", rev = "dea8d97d5ed09bdb6673cb64d0a63706f71c2f61" }
|
|
|
|
|
zcash_history = { git = "https://github.com/ZcashFoundation/librustzcash.git", rev = "dea8d97d5ed09bdb6673cb64d0a63706f71c2f61" }
|
|
|
|
|
|
|
|
|
|
# TODO: remove these after a new librustzcash release (#2982)
|
2021-11-19 15:02:56 -08:00
|
|
|
|
|
|
|
|
# These are librustzcash git requirements specified in its workspace Cargo.toml,
|
|
|
|
|
# that we must replicate here
|
|
|
|
|
incrementalmerkletree = { git = "https://github.com/zcash/incrementalmerkletree.git", rev = "b7bd6246122a6e9ace8edb51553fbf5228906cbb" }
|
|
|
|
|
# Replaced by the ZcashFoundation fork above
|
|
|
|
|
#orchard = { git = "https://github.com/zcash/orchard.git", rev = "2c8241f25b943aa05203eacf9905db117c69bd29" }
|
|
|
|
|
|
2021-11-25 08:26:32 -08:00
|
|
|
# Replaced by the ZcashFoundation fork above
|
|
|
|
|
|
2021-11-19 15:02:56 -08:00
|
|
|
# These are librustzcash file requirements specified in its workspace Cargo.toml,
|
|
|
|
|
# that we must replace with git requirements
|
2021-11-25 08:26:32 -08:00
|
|
|
#zcash_note_encryption = { git = "https://github.com/zcash/librustzcash.git", rev = "53d0a51d33a421cb76d3e3124d1e4c1c9036068e" }
|
2021-11-19 15:02:56 -08:00
|
|
|
|
|
|
|
|
# These patches are not strictly required,
|
|
|
|
|
# but they help avoid duplicate dependencies
|
2021-11-25 08:26:32 -08:00
|
|
|
#equihash = { git = "https://github.com/zcash/librustzcash.git", rev = "53d0a51d33a421cb76d3e3124d1e4c1c9036068e" }
|
|
|
|
|
#zcash_history = { git = "https://github.com/zcash/librustzcash.git", rev = "53d0a51d33a421cb76d3e3124d1e4c1c9036068e" }
|
|
|
|
|
#zcash_primitives = { git = "https://github.com/zcash/librustzcash.git", rev = "53d0a51d33a421cb76d3e3124d1e4c1c9036068e" }
|
|
|
|
|
#zcash_proofs = { git = "https://github.com/zcash/librustzcash.git", rev = "53d0a51d33a421cb76d3e3124d1e4c1c9036068e" }
|
