Commit fb5bfed26a564014b83ccfc96ff00b630930fc61 in #29058 will cause -netinfo
to break when calling it on a node that is running pre-v26 bitcoind, as getpeerinfo
doesn’t yet return a “transport_protocol_type” field.
Fix this by adding an IsNull()
check, as already done for other recent getpeerinfo fields, and also in the same commit:
a) avoid checking for the full string “detecting”, and instead do the cheaper check for the most frequent case of the string starting with “v”
b) drop displaying the “v” prefix in all the rows, as it doesn’t add useful information, and instead use “v” for the column header
c) display nothing when a value isn’t determined yet, like for the -netinfo mping and ping columns (as *
already has a separate meaning in this dashboard, and ?
might look like there is a bug)