lighthouse-pulse/beacon_node
Age Manning fc7a1a7dc7 Allow disconnected states to introduce new peers without warning (#2922)
## Issue Addressed

We emit a warning to verify that all peer connection state information is consistent. A warning is given under one edge case;
We try to dial a peer with peer-id X and multiaddr Y. The peer responds to multiaddr Y with a different peer-id, Z. The dialing to the peer fails, but libp2p injects the failed attempt as peer-id Z. 

In this instance, our PeerDB tries to add a new peer in the disconnected state under a previously unknown peer-id. This is harmless and so this PR permits this behaviour without logging a warning.
2022-01-20 09:14:25 +00:00
..
beacon_chain Update to spec v1.1.8 (#2893) 2022-01-19 00:24:19 +00:00
client Additional networking metrics (#2549) 2021-12-22 06:17:14 +00:00
eth1 Bump crate versions (#2829) 2021-12-02 14:29:57 +11:00
execution_layer Rust 1.58 lints (#2906) 2022-01-13 22:39:58 +00:00
genesis Bump crate versions (#2829) 2021-12-02 14:29:57 +11:00
http_api Support duplicate keys in HTTP API query strings (#2908) 2022-01-20 09:14:19 +00:00
http_metrics Additional networking metrics (#2549) 2021-12-22 06:17:14 +00:00
lighthouse_network Allow disconnected states to introduce new peers without warning (#2922) 2022-01-20 09:14:25 +00:00
network Lazy hashing for SignedBeaconBlock in sync (#2916) 2022-01-14 07:20:54 +00:00
operation_pool Bump crate versions (#2829) 2021-12-02 14:29:57 +11:00
src Update to spec v1.1.8 (#2893) 2022-01-19 00:24:19 +00:00
store Additional networking metrics (#2549) 2021-12-22 06:17:14 +00:00
tests Altair consensus changes and refactors (#2279) 2021-07-09 06:15:32 +00:00
timer Update Lighthouse Dependencies (#2818) 2021-11-18 05:08:42 +00:00
Cargo.toml v2.1.0 (#2928) 2022-01-20 03:39:41 +00:00