aboutsummaryrefslogtreecommitdiff
path: root/doc/bips.md
diff options
context:
space:
mode:
authorPieter Wuille <pieter.wuille@gmail.com>2017-10-18 02:32:16 -0700
committerPieter Wuille <pieter.wuille@gmail.com>2017-10-18 02:37:46 -0700
commit26fee4f6bd9aec62c6caa60683ad66574cf16aa6 (patch)
tree563ff2a3e4ffdd18d0b953c6ffdc8e4042e54102 /doc/bips.md
parent808c84f89d0edcef9ddaab0b849a382719f6ec9e (diff)
parent258d33b41a27917f59e3aee856d032a23cbb5b05 (diff)
Merge #11062: [mempool] Mark mempool import fails that were found in mempool as 'already there'
258d33b41 [mempool] Mark unaccepted txs present in mempool as 'already there'. (Karl-Johan Alm) Pull request description: I was investigating the reasons for failed imports in mempool and noticed that `LoadMempool()` and `pwallet->postInitProcess()` (for all wallets) are executed concurrently. The wallet will end up importing transactions that `LoadMempool()` later tries to import; the latter will fail due to the tx already being in the mempool. This PR changes the log message, adding an additional "already there" entry. For transactions not accepted into mempool, a check if they are in the mempool is done first, and if found, they are counted as 'already there', otherwise counted as 'failed'. Also slight rewording for consistency (successes, failed, expired, ... -> succeeded, failed, expired). Tree-SHA512: 1a6134a25260917f2768365e0dfd8b278fe3f8287cab38bb028b7de3d517718a2d37696186dc7a23ceab338cc755fbbe7d45358ee94e573610fddd2a0620d6e5
Diffstat (limited to 'doc/bips.md')
0 files changed, 0 insertions, 0 deletions