Release notes
*Sourced from [github.com/libp2p/go-libp2p-kad-dht's releases](https://github.com/libp2p/go-libp2p-kad-dht/releases).*
> ## v0.3.2
> * Update several dependencies.
> * Return a signal channel from `RefreshRoutingTable()` that can be waited on to wait for the routing table refresh to complete.
>
> ## v0.3.1
> This is a small patch release to bubble up some updates in dependencies and re-generate the protobuf decoding code.
>
> ## v0.3.0
> This release introduces some significant improvements (and a few breaking changes) to the logic around refreshing the routing tables (previously known as "bootstrapping").
>
> This was previously called "bootstrapping" but bootstrapping and refreshing the routing tables are two separate operations:
> * Bootstrapping is the process of connecting to a set of initial nodes to join the DHT. The DHT doesn't currently perform any bootstrapping internally.
> * Refreshing is the process of filling out the routing table.
>
> Behavior Changes:
>
> * The DHT now automatically starts refreshing the routing table as soon as it's started so there's no need to call `Bootstrap`.
> * The DHT will now refresh the routing table as soon as it sees a new peer as long as we have less than 4 peers in the routing table. This helps us quickly re-build the routing table if we disconnect then reconnect to the network.
> * The DHT now implements the refreshing algorithm described in the Kademlia paper. This should ensure that the routing table remains full.
>
> Breaking API Changes:
>
> * The global NumBootstrapQueries has been removed. The official
> * The `BootstrapWithConfig` function has been removed as bootstrapping is now started immediately after constructing the DHT.
> * The global `BootstrapConfig` type has been removed along with `BootstrapWithConfig`:
> * The config options changed as the old ones didn't make sense given the new algorithm.
> * The config options can now be passed in via the constructor using functional arguments.
> * `BootstrapSelf` has been removed. This was not an effective way to bootstrap the DHT and all users should just call `Refresh()`.
> * `BootstrapRandom` has been removed in favor of `Refresh()`.
> * `BootstrapOnce` has been removed in favor of `Refresh()`.
> * The global `DefaultBootstrapConfig` has been removed along with the `BootstrapConfig` type.
>
> Upgrade Notes:
>
> * You no longer need to call any of the `Bootstrap` methods. If you want force the DHT to fill out its routing table, call `Refresh()`.
> * You can now configure routing table refreshing using the following options when constructing the DHT:
> * DisableAutoRefresh - Never automatically refresh the routing tables. If you pass this, you'll need to manually invoke `Refresh()` as needed.
> * RoutingTableRefreshPeriod - How frequently we should refresh the routing table.
> * RoutingTableRefreshQueryTimeout - how long to run each query during the refresh process before timing it out.
>
> Thanks: I want to give a huge shout-out to a new contributor, [@aarshkshah1992](https://github.com/aarshkshah1992), for making all these changes happen.
>
> ## v0.2.2
> * Introduces the [`opts.BucketSize()`](https://godoc.org/github.com/libp2p/go-libp2p-kad-dht/opts#BucketSize) option to make the bucket size configurable.
Commits
- [`6028925`](https://github.com/libp2p/go-libp2p-kad-dht/commit/60289250205504fe91c44b0ed96e2f6921930878) Merge pull request [#418](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/418) from libp2p/feat/refresh-and-wait
- [`50a9858`](https://github.com/libp2p/go-libp2p-kad-dht/commit/50a9858ef6c14a87bc0d54d116bb9117b86b5411) feat(dht): switch to a single RefreshRoutingTable function returning a channel
- [`0be0cbc`](https://github.com/libp2p/go-libp2p-kad-dht/commit/0be0cbc50e462d576a62436fdf9b6cf677f1c6ce) feat: refresh and wait
- [`6a005f4`](https://github.com/libp2p/go-libp2p-kad-dht/commit/6a005f4687485b7f3a8b18b18785d3b6b1e99b93) Merge pull request [#414](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/414) from libp2p/dependabot/go_modules/go.opencensus.io-0....
- [`1443174`](https://github.com/libp2p/go-libp2p-kad-dht/commit/144317432ce25de275c9d5f80b6789cad413da6e) build(deps): bump go.opencensus.io from 0.22.1 to 0.22.2
- [`1320b07`](https://github.com/libp2p/go-libp2p-kad-dht/commit/1320b0796602519079c8a3b707599f2c632c81b1) Merge pull request [#412](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/412) from libp2p/dependabot/go_modules/github.com/stretchr...
- [`da497ef`](https://github.com/libp2p/go-libp2p-kad-dht/commit/da497efa3dd40f00a5c11f835e02c06f5a244e2f) Merge pull request [#413](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/413) from libp2p/dependabot/go_modules/github.com/mr-tron/...
- [`5233f33`](https://github.com/libp2p/go-libp2p-kad-dht/commit/5233f33ee9eccccedd4296eb5da05a1e1df8b35c) Merge branch 'ci/go-1.13'
- [`24833c8`](https://github.com/libp2p/go-libp2p-kad-dht/commit/24833c83b3c95e2d753955c232480f5f7e2e5ebe) ci: bump to go 1.13
- [`9d48dac`](https://github.com/libp2p/go-libp2p-kad-dht/commit/9d48dac160891c678018ffde45c23320c122eb68) Merge pull request [#415](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/415) from libp2p/dependabot/go_modules/github.com/ipfs/go-...
- Additional commits viewable in [compare view](https://github.com/libp2p/go-libp2p-kad-dht/compare/v0.2.1...v0.3.2)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps github.com/libp2p/go-libp2p-kad-dht from 0.2.1 to 0.3.2.
Release notes
*Sourced from [github.com/libp2p/go-libp2p-kad-dht's releases](https://github.com/libp2p/go-libp2p-kad-dht/releases).* > ## v0.3.2 > * Update several dependencies. > * Return a signal channel from `RefreshRoutingTable()` that can be waited on to wait for the routing table refresh to complete. > > ## v0.3.1 > This is a small patch release to bubble up some updates in dependencies and re-generate the protobuf decoding code. > > ## v0.3.0 > This release introduces some significant improvements (and a few breaking changes) to the logic around refreshing the routing tables (previously known as "bootstrapping"). > > This was previously called "bootstrapping" but bootstrapping and refreshing the routing tables are two separate operations: > * Bootstrapping is the process of connecting to a set of initial nodes to join the DHT. The DHT doesn't currently perform any bootstrapping internally. > * Refreshing is the process of filling out the routing table. > > Behavior Changes: > > * The DHT now automatically starts refreshing the routing table as soon as it's started so there's no need to call `Bootstrap`. > * The DHT will now refresh the routing table as soon as it sees a new peer as long as we have less than 4 peers in the routing table. This helps us quickly re-build the routing table if we disconnect then reconnect to the network. > * The DHT now implements the refreshing algorithm described in the Kademlia paper. This should ensure that the routing table remains full. > > Breaking API Changes: > > * The global NumBootstrapQueries has been removed. The official > * The `BootstrapWithConfig` function has been removed as bootstrapping is now started immediately after constructing the DHT. > * The global `BootstrapConfig` type has been removed along with `BootstrapWithConfig`: > * The config options changed as the old ones didn't make sense given the new algorithm. > * The config options can now be passed in via the constructor using functional arguments. > * `BootstrapSelf` has been removed. This was not an effective way to bootstrap the DHT and all users should just call `Refresh()`. > * `BootstrapRandom` has been removed in favor of `Refresh()`. > * `BootstrapOnce` has been removed in favor of `Refresh()`. > * The global `DefaultBootstrapConfig` has been removed along with the `BootstrapConfig` type. > > Upgrade Notes: > > * You no longer need to call any of the `Bootstrap` methods. If you want force the DHT to fill out its routing table, call `Refresh()`. > * You can now configure routing table refreshing using the following options when constructing the DHT: > * DisableAutoRefresh - Never automatically refresh the routing tables. If you pass this, you'll need to manually invoke `Refresh()` as needed. > * RoutingTableRefreshPeriod - How frequently we should refresh the routing table. > * RoutingTableRefreshQueryTimeout - how long to run each query during the refresh process before timing it out. > > Thanks: I want to give a huge shout-out to a new contributor, [@aarshkshah1992](https://github.com/aarshkshah1992), for making all these changes happen. > > ## v0.2.2 > * Introduces the [`opts.BucketSize()`](https://godoc.org/github.com/libp2p/go-libp2p-kad-dht/opts#BucketSize) option to make the bucket size configurable.Commits
- [`6028925`](https://github.com/libp2p/go-libp2p-kad-dht/commit/60289250205504fe91c44b0ed96e2f6921930878) Merge pull request [#418](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/418) from libp2p/feat/refresh-and-wait - [`50a9858`](https://github.com/libp2p/go-libp2p-kad-dht/commit/50a9858ef6c14a87bc0d54d116bb9117b86b5411) feat(dht): switch to a single RefreshRoutingTable function returning a channel - [`0be0cbc`](https://github.com/libp2p/go-libp2p-kad-dht/commit/0be0cbc50e462d576a62436fdf9b6cf677f1c6ce) feat: refresh and wait - [`6a005f4`](https://github.com/libp2p/go-libp2p-kad-dht/commit/6a005f4687485b7f3a8b18b18785d3b6b1e99b93) Merge pull request [#414](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/414) from libp2p/dependabot/go_modules/go.opencensus.io-0.... - [`1443174`](https://github.com/libp2p/go-libp2p-kad-dht/commit/144317432ce25de275c9d5f80b6789cad413da6e) build(deps): bump go.opencensus.io from 0.22.1 to 0.22.2 - [`1320b07`](https://github.com/libp2p/go-libp2p-kad-dht/commit/1320b0796602519079c8a3b707599f2c632c81b1) Merge pull request [#412](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/412) from libp2p/dependabot/go_modules/github.com/stretchr... - [`da497ef`](https://github.com/libp2p/go-libp2p-kad-dht/commit/da497efa3dd40f00a5c11f835e02c06f5a244e2f) Merge pull request [#413](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/413) from libp2p/dependabot/go_modules/github.com/mr-tron/... - [`5233f33`](https://github.com/libp2p/go-libp2p-kad-dht/commit/5233f33ee9eccccedd4296eb5da05a1e1df8b35c) Merge branch 'ci/go-1.13' - [`24833c8`](https://github.com/libp2p/go-libp2p-kad-dht/commit/24833c83b3c95e2d753955c232480f5f7e2e5ebe) ci: bump to go 1.13 - [`9d48dac`](https://github.com/libp2p/go-libp2p-kad-dht/commit/9d48dac160891c678018ffde45c23320c122eb68) Merge pull request [#415](https://github-redirect.dependabot.com/libp2p/go-libp2p-kad-dht/issues/415) from libp2p/dependabot/go_modules/github.com/ipfs/go-... - Additional commits viewable in [compare view](https://github.com/libp2p/go-libp2p-kad-dht/compare/v0.2.1...v0.3.2)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)