update librustzcash #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
release zcash_client_backend version 0.13.0
release zcash_client_sqlite version 0.11.0
zcash_client_sqlite: Fix migration DAG edges
release zcash_client_sqlite version 0.11.1
…utChangeStrategy` doc comments more accurate concerning the choice of output pool. Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
These operations are unused, and block heights form a vector space, not a monoid.
zcash_client_sqlite: Add missing test of `utxos_to_txos` migration.
zcash_protocol: Remove impl {Add, Sub} for BlockHeight
zcash_protocol: Set the public testnet activation height for NU6
Release zcash_protocol version 0.3.0
Release zcash_address version 0.5.0
…-merge Merge hotfix/zcash_client_sqlite-0.12.x back to `main`.
Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
…test profile to compile with optimizations by default, but keep full debug info. This differs from the release profile in the following ways: - it does not set `lto = true`, which increases compile times without substantially speeding up tests; - it does not set `codegen-units = 1`, which increases compile times and is only useful to improve determinism of release builds; - it does not set `panic = 'abort'`, which is in any case ignored for tests. After this PR, to get results as close as possible to a release build, use `cargo test --release`. To speed up compilation and avoid optimizations potentially resulting in lower-quality debug info, use `cargo test --profile=dev`. Times on my machine starting from `cargo clean` for each run: * `cargo test --all-targets --all-features`: * 484s (354s build, 130s tests) * `cargo test --release --all-targets --all-features`: * 541s (415s build, 126s tests) * `cargo test --profile=dev --all-targets --all-features`: * 1709s (146s build, 1563s tests) * this might still be faster when running individual tests. Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
(instead of only in CI), so that there is no need to set it manually. You can override this by setting `RUST_BACKTRACE=0`, or `RUST_BACKTRACE=full` for a full backtrace. Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
Dev quality-of-life improvements (better test backtraces in CI and locally; faster test builds; `RUST_BACKTRACE=1` by default)
* Fix the documentation for `find_account_for_ephemeral_address` which included a use of `get_known_ephemeral_addresses` with incorrect types. * Clarify that passing `None` for the `index_range` parameter of `get_known_ephemeral_addresses` is equivalent to passing `0..(1u32 << 31)`. Signed-off-by: Daira-Emma Hopwood <daira@katava.local>
[doc-only] Minor documentation fix and clarification for the data API
This generalizes the previous account metadata query API to be able to represent more complex queries, and also to return note totals in addition to note counts.
Co-authored by: Jack Grig <jack@electriccoin.co> Co-authored-by: Daira-Emma Hopwood <daira@jacaranda.org>
…n_split zcash_client_backend: Generalize & extend wallet metadata query API
This reverts the MSRV update for the `zcash_protocol` crate; no MSRV-breaking changes have been made, and retaining the 1.70 MSRV allows us to make this a semver-compatible release.
Release zcash_protocol version 0.4.1
Release zcash_proofs version 0.20.0
Release zcash_keys version 0.5.0
Release zcash_client_backend version 0.15.0
Release/zcash client sqlite 0.13.0
Release zcash_primitives version 0.20.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.