diff options
author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-05-07 12:45:33 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-05-07 12:49:11 +0200 |
commit | a174702bad1c7f09830df592346e55cab676dbb2 (patch) | |
tree | b90c97d7ef2d744e982f7cf16414c5a4f29c5213 /test | |
parent | 66cc47be982aa431b72494f5d655c20eea17a0f5 (diff) | |
parent | fad63ebe0f0db1e1d909064665be91ebd970bb0a (diff) |
Merge #13162: [net] Don't incorrectly log that REJECT messages are unknown.
fad63eb [logging] Don't incorrectly log that REJECT messages are unknown. (John Newbery)
Pull request description:
Reject messages are logged to debug.log if NET debug logging is enabled.
Because of the way the `ProcessMessages()` function is structured,
processing for REJECT messages will also drop through to the default
branch and incorrectly log `Unknown command "reject" from peer-?`. Fix
that by exiting from `ProcessMessages()` early.
without this PR:
```
2018-05-03T17:37:00.930600Z received: reject (21 bytes) peer=0
2018-05-03T17:37:00.930620Z Reject message code 16: spammy spam
2018-05-03T17:37:00.930656Z Unknown command "reject" from peer=0
```
with this PR:
```
2018-05-03T17:35:04.751246Z received: reject (21 bytes) peer=0
2018-05-03T17:35:04.751274Z Reject message code 16: spammy spam
```
Tree-SHA512: 5c84c98433ab99e0db2dd481f9c2db6f87ff0d39022ff317a791737e918714bbcb4a23e81118212ed8e594ebcf098ab7f52f7fd5e21ebc3f07b1efb279b9b30b
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions