aboutsummaryrefslogtreecommitdiff
path: root/src/cryptonote_core
diff options
context:
space:
mode:
authormoneromooo-monero <moneromooo-monero@users.noreply.github.com>2017-02-13 19:05:30 +0000
committermoneromooo-monero <moneromooo-monero@users.noreply.github.com>2017-02-13 19:05:30 +0000
commitcca95c1c7aa7506c7ec0df9846807050911152eb (patch)
treef47e98f5a10ac9f3a31bc4e753d70da005fff141 /src/cryptonote_core
parentMerge pull request #1718 (diff)
downloadmonero-cca95c1c7aa7506c7ec0df9846807050911152eb.tar.xz
blockchain_db: do not throw on expected partial results getting keys
When scanning for outputs used in a set of incoming blocks, we expect that some of the inputs in their transactions will not be found in the blockchain, as they could be in previous blocks in that set. Those outputs will be scanned there at a later point. In this case, we add a flag to control wehther an output not being found is expected or not.
Diffstat (limited to 'src/cryptonote_core')
-rw-r--r--src/cryptonote_core/blockchain.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cryptonote_core/blockchain.cpp b/src/cryptonote_core/blockchain.cpp
index a81286632..d67c5f2b2 100644
--- a/src/cryptonote_core/blockchain.cpp
+++ b/src/cryptonote_core/blockchain.cpp
@@ -3540,7 +3540,7 @@ void Blockchain::output_scan_worker(const uint64_t amount, const std::vector<uin
{
try
{
- m_db->get_output_key(amount, offsets, outputs);
+ m_db->get_output_key(amount, offsets, outputs, true);
}
catch (const std::exception& e)
{