Added comments for easier reading.
(I have further pull request coming which adds additional variables for further diagnosis of timings and delays in downloading from other peers).
Added comments for easier reading.
(I have further pull request coming which adds additional variables for further diagnosis of timings and delays in downloading from other peers).
206 | @@ -207,10 +207,10 @@ class CNode 207 | uint64_t nRecvBytes; 208 | int nRecvVersion; 209 | 210 | - int64_t nLastSend; 211 | - int64_t nLastRecv; 212 | - int64_t nLastSendEmpty; 213 | - int64_t nTimeConnected; 214 | + int64_t nLastSend; // Time data last sent to peer.
Not sure whether it's already used, but it should be used.
See http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html
It's also mentioned in doc/coding-style.md
Apologies, these are about message sends, not pings.
Automatic sanity-testing: FAILED MERGE, see http://jenkins.bluematt.me/pull-tester/p4200_fd97466c72709abf4c21008d69a73ced48c99357/ for test log.
This pull does not merge cleanly onto current master This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Needs rebase + nit fix