GitLab

Otherwise, we'll just return a channel that will never be signaled.

chore(dep): update kbucket

Fixes a bug where we wouldn't be able to perform queries with a sparse but
non-empty routing table.

fix: try to re-add existing peers when the routing table is empty

Otherwise, we could decide to _not_ add a peer, disconnect from most peers, and
be unable to query the DHT even if we're technically connected to a peer in the
DHT.

Merge pull request #419 from libp2p/dependabot/go_modules/github.com/multiformats/go-multiaddr-0.2.0

build(deps): bump github.com/multiformats/go-multiaddr from 0.1.2 to 0.2.0

Bumps [github.com/multiformats/go-multiaddr](https://github.com/multiformats/go-multiaddr) from 0.1.2 to 0.2.0.
- [Release notes](https://github.com/multiformats/go-multiaddr/releases)
- [Commits](https://github.com/multiformats/go-multiaddr/compare/v0.1.2...v0.2.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

feat: refresh and wait

We'd like to be able to refresh then _wait_ for the refresh to finish in the testground DHT tests. That way, we can:

1. Start and disable _auto_ refresh.
2. Bootstrap.
3. Refresh a couple of times till we're stable.
4. Wait to _stop_ refreshing.
5. Disconnect from and forget about all peers _not_ in our routing tables.
6. Run the actual tests without interference from the bootstrapping logic.

build(deps): bump go.opencensus.io from 0.22.1 to 0.22.2

Bumps [go.opencensus.io](https://github.com/census-instrumentation/opencensus-go) from 0.22.1 to 0.22.2.
- [Release notes](https://github.com/census-instrumentation/opencensus-go/releases)
- [Commits](https://github.com/census-instrumentation/opencensus-go/compare/v0.22.1...v0.22.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

build(deps): bump github.com/stretchr/testify from 1.3.0 to 1.4.0

build(deps): bump github.com/mr-tron/base58 from 1.1.2 to 1.1.3

build(deps): bump github.com/ipfs/go-datastore from 0.1.1 to 0.3.1

Bumps [github.com/ipfs/go-datastore](https://github.com/ipfs/go-datastore) from 0.1.1 to 0.3.1.
- [Release notes](https://github.com/ipfs/go-datastore/releases)
- [Commits](https://github.com/ipfs/go-datastore/compare/v0.1.1...v0.3.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [github.com/mr-tron/base58](https://github.com/mr-tron/base58) from 1.1.2 to 1.1.3.
- [Release notes](https://github.com/mr-tron/base58/releases)
- [Commits](https://github.com/mr-tron/base58/compare/v1.1.2...v1.1.3)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.3.0 to 1.4.0.
- [Release notes](https://github.com/stretchr/testify/releases)
- [Commits](https://github.com/stretchr/testify/compare/v1.3.0...v1.4.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore(dep): update

Update deps:

* Switch to multiformats/go-base32
* Regenerate protobuf decoding code

Make max record age configurable

fix and simplify some bootstrapping logic

As pointed out by raul, bootstrapping and refreshing are not the same thing.
Bootstrapping is the initial setup (i.e., connect to some initial nodes to get
started). Refreshing is the process of refreshing the routing table.

We can't generate target IDs in buckets beyond bucket 15 so there's no point.

The default timeout is 10s so this won't take that long anyways. On the
other hand, if we do this all at once, we max the swarms dial queue.

* Rename triggerAutoBootstrap to autoBootstrap. This variable used to control
_triggering_ only but now completely disables automatic bootstrapping.
* Remove the BootstrapConfig. We introduced this before we switched to
functional options. Now that we're breaking the interfaces anyways, we might as
well use functional options all the way (easier to extend).
* Always query self (feedback from @raulk).
* Important: don't abort the bootstrap process if we timeout finding ourselves.

feat(bootstrap): take autobootstrap to completion