aboutsummaryrefslogtreecommitdiff
path: root/test/functional/p2p_v2_misbehaving.py
diff options
context:
space:
mode:
authorMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2024-07-23 19:37:26 +0200
committerMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2024-07-23 19:37:59 +0200
commit55555574d105f6c529c5c966c3c971c9db5ab786 (patch)
tree9562ce801c7754bf0b89f6ad7f33d8029e0d9d5c /test/functional/p2p_v2_misbehaving.py
parent910d38b22f575cba9a3325de3f4c5ac667d4a487 (diff)
net: Log accepted connection after m_nodes.push_back
Otherwise, the debug log could read confusingly, when the getpeerinfo() RPC (calling GetNodeStats) happens after the "accepted connection" log line, but returns an empty list. For example, the following timeline in the debug log could correspond to a getpeerinfo reply that is empty: [net] [net.cpp:3764] [CNode] Added connection peer=0 [net] [net.cpp:1814] [CreateNodeFromAcceptedSocket] connection from 127.0.0.1:45154 accepted [http] [httpserver.cpp:305] [http_request_cb] Received a POST request for / from 127.0.0.1:33320 [httpworker.1] [rpc/request.cpp:232] [parse] ThreadRPCServer method=getpeerinfo user=__cookie__ Fix it by moving the log line.
Diffstat (limited to 'test/functional/p2p_v2_misbehaving.py')
0 files changed, 0 insertions, 0 deletions