Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Fix headers announcements edge case #7919
Conversation
|
utACK |
jonasschnelli
added
the
P2P
label
Apr 21, 2016
|
utACK 3a99fb2 |
|
utACK 3a99fb2 |
|
utACK 3a99fb2 |
|
utACK 3a99fb2 On April 20, 2016 11:26:28 AM PDT, Suhas Daftuar notifications@github.com wrote:
|
laanwj
added
the
Needs backport
label
Apr 22, 2016
laanwj
merged commit 3a99fb2
into
bitcoin:master
Apr 22, 2016
1 check passed
added a commit
that referenced
this pull request
Apr 22, 2016
added a commit
to MarcoFalke/bitcoin
that referenced
this pull request
Apr 27, 2016
|
Backported as part of #7938. Removing label 'Needs backport'. |
sdaftuar commentedApr 20, 2016
Previously we would assert that if every block in
vBlockHashesToAnnounceis inchainActive, then the blocks to be announced must connect. However, there areedge cases where this assumption could be violated (eg using invalidateblock /
reconsiderblock), so just check for this case and revert to inv-announcement
instead.
FYI I encountered this bug once while running
mempool_packages.py, and was able to reproduce reliably by repeatedly invokinginvalidateblock/reconsiderblockon the tip.Perhaps we should backport this to 0.12 as well?