fix DHT connection on discovery on devnet

[noot]

Task summary

• DHT discovery seems to have regressed on the devnet and no longer works
• previously, when running 3 nodes Alice, Bob and Charlie, Bob and Charlie would use Alice as their bootnode, and then discover each other via the DHT, resulting in each node having 2 peers
• however it seems to have regressed w/ the peer scoring update and this no longer happens (Alice has 2 peers, but Bob and Charlie only have 1, and they no longer connect to each other)
• it seems they still discover each other, but don't connect to each other, as adding in code to directly connect them after discovering results in the correct behaviour (ie. adding a line here to connect them, as can be seen in older commits)
  

  gossamer/dot/network/discovery.go

  Lines 212 to 221 in d7147cf

  	if len(d.h.Network().Peers()) < d.maxPeers {
  	err = d.h.Connect(d.ctx, peer)
  	if err != nil {
  	logger.Trace("failed to connect to discovered peer", "peer", peer.ID, "err", err)
  	}
  	} else {
  	d.h.Peerstore().AddAddrs(peer.ID, peer.Addrs, peerstore.PermanentAddrTTL)
  	return
  	}
  	}

[github-actions]

🎉 This issue has been resolved in version 0.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀