net: Fix sent reject messages for blocks and transactions#7179
net: Fix sent reject messages for blocks and transactions#7179laanwj merged 2 commits intobitcoin:masterfrom
Conversation
Ever since we bitcoin#5913 have been sending invalid reject messages for transactions and blocks.
|
Worth adding a regression test? |
|
Would make sense. |
|
To be clear, this solves the following issue: Normal reject message Reject message from 0.11.99+ Reason seems empty, and part of the reason message ends up in the "hash". This is due to the reject code being sent as multiple bytes instead of one, misaligning the message. Edit: trying to think of a test. Hopefully it could fit somewhere in the Python P2P test framework, without creating a new script. |
|
utACK 9fc6ed6 |
|
Added basic tests for rejection of blocks and transactions. |
40811fe to
5eea9ce
Compare
Extend P2P test framework to make it possible to expect reject codes for transactions and blocks.
5eea9ce to
2041190
Compare
|
@sdaftuar Mind taking a look at the test changes? |
|
Sure, will take a look.
|
|
post-merge ACK. The extension to the test framework seems like a good idea! |
Extend P2P test framework to make it possible to expect reject codes for transactions and blocks. Github-Pull: bitcoin#7179 Rebased-From: 2041190
Extend P2P test framework to make it possible to expect reject codes for transactions and blocks. Github-Pull: bitcoin#7179 Rebased-From: 2041190
|
This is cherry-picked to 0.12 as 44fef99, removing needs backport label |
ZIP 239 preparations 4 Cherry-picked from the following upstream PRs: - bitcoin/bitcoin#5913 - Replaces #3111. - Includes an extra commit included by upstream in the merge outside the PR. - bitcoin/bitcoin#6519 - bitcoin/bitcoin#7179 - bitcoin/bitcoin#7853 - bitcoin/bitcoin#7960
Ever since we #5913 have been sending invalid reject messages for transactions and blocks.