GitLab

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

PoC of Bitswap protocol extensions implementation

This commit extends the bitswap protocol with two additional wantlist properties:

* WANT_HAVE/HAVE: Instead of asking for a block, a node can specify that they
  want to know if any peers "have" the block.
* WANT_HAVE_NOT/HAVE_NOT: Instead of waiting for a timeout, a node can explicitly
  request to be told immediately if their peers don't currently have the given
  block.

Additionally, nodes now tell their peers how much data they have queued to send
them when sending messages. This allows peers to better distribute requests,
keeping all peers busy but not overloaded.

Changes in this PR are described in: https://github.com/ipfs/go-bitswap/issues/186

fix: abort when the context is canceled while getting blocks

chore(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>

chore(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>

chore(deps): bump github.com/libp2p/go-libp2p-testing from 0.1.0 to 0.1.1

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

fix: wait until we finish connecting before we cancel the context

This is an interesting bug because changes to the DHT have suddenly started
triggering it. I'm not sure _why_ we weren't hitting it before now.

We may have been ignoring a context somewhere?

* feat: parallelize reads

* feat: concurent engine task workers and concurrent bstore reads

* fix: lint

* fix: address review comments

* refactor: in BlockstoreManager wait for process.Closing() instead of Context.Done()

* fix: use channel size 0 for BlockstoreManager reads

* fix: change blockstore error logs from warnings to errors

* fix: flaky test

* fix: lint

chore(deps): bump github.com/gogo/protobuf from 1.3.0 to 1.3.1

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

chore(deps): bump github.com/libp2p/go-libp2p from 0.1.1 to 0.4.0

Bumps [github.com/libp2p/go-libp2p](https://github.com/libp2p/go-libp2p) from 0.1.1 to 0.4.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.1.1...v0.4.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

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

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

chore(deps): bump github.com/gogo/protobuf from 1.2.1 to 1.3.0

chore(deps): bump github.com/ipfs/go-ipfs-blockstore from 0.0.1 to 0.1.0

Bumps [github.com/ipfs/go-ipfs-blockstore](https://github.com/ipfs/go-ipfs-blockstore) from 0.0.1 to 0.1.0.
- [Release notes](https://github.com/ipfs/go-ipfs-blockstore/releases)
- [Commits](https://github.com/ipfs/go-ipfs-blockstore/compare/v0.0.1...v0.1.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore(deps): bump github.com/ipfs/go-datastore from 0.0.5 to 0.1.0

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

chore(deps): bump github.com/ipfs/go-cid from 0.0.2 to 0.0.3

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

Bumps [github.com/ipfs/go-cid](https://github.com/ipfs/go-cid) from 0.0.2 to 0.0.3.
- [Release notes](https://github.com/ipfs/go-cid/releases)
- [Commits](https://github.com/ipfs/go-cid/compare/v0.0.2...v0.0.3)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Add bridged chats

engine: tag peers based on usefulness

* doc: add dirk as the lead maintainer

One of my tasks this quarter is to get a lead maintainer for each repo.

This patch tracks two usefulness metrics: short-term usefulness and long-term
usefulness. Short-term usefulness is sampled frequently and highly weights new
observations. Long-term usefulness is sampled less frequently and highly weights
on long-term trends.

In practice, we do this by keeping two EWMAs. If we see an interaction within
the sampling period, we record the score, otherwise, we record a 0. The
short-term one has a high alpha and is sampled every shortTerm period. The
long-term one has a low alpha and is sampled every longTermRatio*shortTerm
period.

To calculate the final score, we sum the short-term and long-term scores then
adjust it ±25% based on our debt ratio. Peers that have historically been more
useful to us than we are to them get the highest score.

reduce session contention

We're not using these synchronously so we can buffer them a bit to avoid
blocking quite as much.

This also combines all incoming channels into a single one to ensure all
operations are processed in-order. This might be overkill bit it makes reasoning
about this a bit simpler.