GitLab

They've told us better ones via identify.

1. When a peer changes their listening addresses, we need to re-run our routing
table filters, possibly removing them.
2. When a peer _starts_ supporting the DHT protocol, we need to add them to our
routing table. Previously, we'd only do the inverse.

intercept failing query events when finding providers

build(deps): bump github.com/ipfs/go-log from 1.0.3 to 1.0.4

Bumps [github.com/ipfs/go-log](https://github.com/ipfs/go-log) from 1.0.3 to 1.0.4.
- [Release notes](https://github.com/ipfs/go-log/releases)
- [Commits](https://github.com/ipfs/go-log/compare/v1.0.3...v1.0.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

feat: set provider manager options

chore: optimize debug logging a bit

build(deps): bump github.com/libp2p/go-libp2p from 0.8.0 to 0.8.1

stricter definition of public for DHT

These are all critical paths so we should try to do as little work as possible.

Bumps [github.com/libp2p/go-libp2p](https://github.com/libp2p/go-libp2p) from 0.8.0 to 0.8.1.
- [Release notes](https://github.com/libp2p/go-libp2p/releases)
- [Changelog](https://github.com/libp2p/go-libp2p/blob/master/NEWS.md)
- [Commits](https://github.com/libp2p/go-libp2p/compare/v0.8.0...v0.8.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Merge pull request #583 from libp2p/dependabot/go_modules/github.com/libp2p/go-libp2p-routing-helpers-0.2.1

build(deps): bump github.com/libp2p/go-libp2p-routing-helpers from 0.2.0 to 0.2.1

build(deps): bump github.com/libp2p/go-libp2p from 0.7.4 to 0.8.0

feat: reduce allocations

After profiling allocations on a bootstrap node, I've noticed that
peerInfoToPBPeer is a very heavy source of allocations. This change should
improve the situation significantly.

Bumps [github.com/libp2p/go-libp2p](https://github.com/libp2p/go-libp2p) from 0.7.4 to 0.8.0.
- [Release notes](https://github.com/libp2p/go-libp2p/releases)
- [Changelog](https://github.com/libp2p/go-libp2p/blob/master/NEWS.md)
- [Commits](https://github.com/libp2p/go-libp2p/compare/v0.7.4...v0.8.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

query.go: Remove shuffle comment

As far as I can tell the list of peers is not being shuffled in this function. In addition [`NearestPeers`](https://github.com/libp2p/go-libp2p-kbucket/blob/a8232c8ad2e784b3966d04f86a28f9223d1d11a8/table.go#L323) returns them in sorted order.

Hope I am not missing something.

fix: optimize isRelay

This function is called frequently, let's avoid allocating as much as possible.

Bumps [github.com/libp2p/go-libp2p-routing-helpers](https://github.com/libp2p/go-libp2p-routing-helpers) from 0.2.0 to 0.2.1.
- [Release notes](https://github.com/libp2p/go-libp2p-routing-helpers/releases)
- [Commits](https://github.com/libp2p/go-libp2p-routing-helpers/compare/v0.2.0...v0.2.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

feat: expose WANActive

fix: improve error handling in dual dht

1. FindPeer should succeed as long as we find the peer in one DHT.
2. If we get a kbucket error from one DHT, return the error from the other DHT.
3. Avoid returning the same error twice.

fix: dedup addresses

That way, external users can easily determine which DHT they should use. E.g.,
in go-ipfs, I'd like to call GetClosestPeers in the `ipfs dht` commands based on
the "active" DHT.

Fix bug in periodic peer pinging

Dual DHT scaffold