Make the inproc channel describe its destination as the peer (#5236) An inproc channel took its node id and protocol version from the node it sends from rather than the node it sends to, so a channel between two nodes named the wrong peer, and the reply channel handed to the receiver named the receiver itself. Only a loopback channel, where the two coincide, got it right, which is why no test noticed. The peer is now the destination, and `inproc.describes_destination` checks it on a channel between two nodes.
__________
Type: commit
Hash: 01a085bedd824f2fe9c789326d54737a9a502f95
Created: today
__________
gr0v1ty/nano-node:01a085bedd824f2fe9c789326d54737a9a502f95
| Test Case | Status | Duration | Median Deviation | Log | Graph |
|---|---|---|---|---|---|
| 5n4pr_conf_10k_bintree | PASS | 111 s | -0.5 s | - | Show |
| 5n4pr_conf_10k_change | PASS | 157 s | 1.5 s | - | Show |
| 5n4pr_conf_change_dependant | PASS | 117 s | 3.5 s | - | - |
| 5n4pr_conf_change_independant | PASS | 105 s | -10.5 s | - | - |
| 5n4pr_conf_send_dependant | PASS | 116 s | 1.0 s | - | - |
| 5n4pr_conf_send_independant | PASS | 107 s | -5.5 s | - | - |
| 5n4pr_rocks_10k_bintree | PASS | 112 s | -0.5 s | - | - |
| 5n4pr_rocks_10k_change | PASS | 191 s | 24.0 s | - | - |