From 03c2e538ca8f317f9a1e8e5bb258ae6c18fbf70d Mon Sep 17 00:00:00 2001 From: Daira-Emma Hopwood Date: Sat, 10 Aug 2024 10:40:36 +0100 Subject: [PATCH] Improve the accuracy of a comment in `send_multi_step_proposed_transfer`. Signed-off-by: Daira-Emma Hopwood --- zcash_client_sqlite/src/testing/pool.rs | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/zcash_client_sqlite/src/testing/pool.rs b/zcash_client_sqlite/src/testing/pool.rs index ca0aa2845..242601993 100644 --- a/zcash_client_sqlite/src/testing/pool.rs +++ b/zcash_client_sqlite/src/testing/pool.rs @@ -685,11 +685,12 @@ pub(crate) fn send_multi_step_proposed_transfer() { // The above `scan_cached_blocks` does not detect `tx` as interesting to the // wallet. If a transaction is in the database with a null `mined_height`, - // as in this case, its `mined_height` will remain null unless `put_tx_meta` - // is called on it. This happens either via `put_blocks` as a result of - // scanning, or via `set_transaction_status` in response to processing the - // `transaction_data_requests` queue. For a fully transparent transaction, - // the latter is required. + // as in this case, its `mined_height` will remain null unless either + // `put_tx_meta` or `set_transaction_status` is called on it. The former + // is normally called internally via `put_blocks` as a result of scanning, + // but not for the case of a fully transparent transaction. The latter is + // called by the wallet implementation in response to processing the + // `transaction_data_requests` queue. // The reservation should fail because `tx` is not yet seen as mined. reservation_should_fail(&mut st, 1, 22);