diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-15 16:55:50 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-15 17:05:43 +0100 |
| commit | 947c25ead21a00f3f9a46bb462ae8bc6fb7a0bb6 (patch) | |
| tree | c9ddbd17f8ec0cd38902962f8dfc7abe246e7785 /build-aux/m4/ax_boost_chrono.m4 | |
| parent | e057589dc67f25da6779b60d0e247a3730adbc6d (diff) | |
| parent | f98b543522687a4ff93ad7d53fa3cc67b5c6d752 (diff) | |
| download | bitcoin-947c25ead21a00f3f9a46bb462ae8bc6fb7a0bb6.tar.xz | |
Merge #12431: Only call NotifyBlockTip when chainActive changes
f98b54352 Only call NotifyBlockTip when the active chain changes (James O'Beirne)
152b7fb25 [tests] Add a (failing) test for waitforblockheight (James O'Beirne)
Pull request description:
This is a subset of the more controversial https://github.com/bitcoin/bitcoin/pull/12407, but this also adds a test demonstrating the bug.
In InvalidateBlock, we're calling NotifyBlockTip with the now-invalid block's prev regardless of what chain the ancestor block is on. This could create numerous issues, but it at least screws up `waitforblockheight` (or anything else relying on `rpc/blockchain.cpp:latestblock`) when InvalidateBlock is called on a block not in chainActive, which can happen via RPC.
Only call NotifyBlockTip when the block being marked invalid is on the active chain.
Tree-SHA512: 9a54fe5e8c7eb489daf5df4483c0986129e871e2ca931a456ba869ecb5d5a8d4f7bd27ccc9e711e9292c9ed79ddef896c85d0e81fc76883503e327995b0e914f
Diffstat (limited to 'build-aux/m4/ax_boost_chrono.m4')
0 files changed, 0 insertions, 0 deletions