ci-work

additional info: ``` 2021-12-16 01:26:31.064 [info] @libp2p_transport_tcp:handle_info:500 retrying stungun with peer "/p2p/116Sa97proLW3oTBwUKtR1k7yxABCCwE3dnxvDwqhkh7snbEu3z" 2021-12-16 01:26:31.242 [info] @libp2p_transport_tcp:handle_info:527 stungun detected NAT type symmetric 2021-12-16 01:26:31.247 [info] @libp2p_relay_server:init_relay:242 initiating relay with peer "/p2p/11x5kNN7RKFEfaqe7TRxXc5bGV2Mz8U4LLwXaHK7hNYA4UZTsXe"...

bump, this issue is still present and one of the causes of issues hotspot owners are complaining about, should be an easy fix

> Want to supply a patch? I don't think I'm best placed to make adjustments here, however it looks to my untrained eye like if the list returned by `libp2p_peer:connected_peers(MyPeer)`...

possible related: https://github.com/helium/erlang-libp2p/issues/376

Indeed, hence why showing sequential blocks here in logs and the restart, I'd always put it down to the same reasons, but then seeing that a series of blocks could...