When no ping received yet, minping value in getpeerinfo is uninitialized (resp. initialized to std::numeric_limits<int64_t>::max()/1e6). Do not print it in such cases.
Document such behaviour (also for pingwait).
Fixes #7837.
When no ping received yet, minping value in getpeerinfo is uninitialized (resp. initialized to std::numeric_limits<int64_t>::max()/1e6). Do not print it in such cases.
Document such behaviour (also for pingwait).
Fixes #7837.
utACK
Just realized: dPingTime suffers from the same problem if there has never been a ping. It gets initialized to zero, but that's just as well a nonsensical value if we really want to be consistent at 'leave out fields that have no value'.
Do you want me to change it in one go?
Do you want me to change it in one go?
I'd say it makes sense, it's basically the same thing.
Force pushed.
Great!
utACK 62a6486
Concept ACK
Tested ACK. New connection has neither minping, pingtime or pingwait.
[
{
"id": 1,
"addr": "127.0.0.1:56078",
"services": "0000000000000000",
"relaytxes": false,
"lastsend": 0,
"lastrecv": 0,
"bytessent": 0,
"bytesrecv": 0,
"conntime": 1460642850,
"timeoffset": 0,
"version": 0,
"subver": "",
"inbound": true,
"startingheight": -1,
"banscore": 0,
"synced_headers": -1,
"synced_blocks": -1,
"inflight": [
],
"whitelisted": false,
"bytessent_per_msg": {
},
"bytesrecv_per_msg": {
}
}
]
posthumous "hey, I was whining about that" ACK.