GitLab

Long-running queries can build up large error sets that we never actually use.
This is exacerbated by https://github.com/libp2p/go-libp2p-swarm/pull/115.

fixes https://github.com/libp2p/go-libp2p-swarm/issues/119

providers: run datastore GC concurrently

Motivation: Walking the datastore can take time and currently blocks
adding/removing providers.

We need to do this in the same goroutine to avoid some logical races.

fix(providers): gc

Otherwise, we'll delete everything.

Remove the old protocol from the defaults

Add initial set of metrics exposed via OpenCensus.

Fix some provider subsystem performance issues

batches deletes

1. Don't be n^2.
2. Don't bother walking the cache, just drop it.

We only access it from a single goroutine.

This is just extra work as we write through anyways.

gomod: update go-libp2p

go-libp2p-peerstore now has a TempAddrTTL of 2 minutes

gomod: update libp2p to v0.0.4

dialQueue: start the control loop later

Don't start the control loop till we start the queue. The _in_ queue will still
work, we just won't start processing peers from it until we start the control loop.

fixes #311

make it work in wasm

Revert "GoModules: Checksum mismatch:"

Go 1.11 has some weird go module checksum issues.

GoModules: Checksum mismatch:

Add go1.12 to TravisCI

```
verifying github.com/ipfs/go-datastore@v0.0.1/go.mod: checksum mismatch
        downloaded: h1:bYmHO9fuKO1Ca7dpdDBWQl0mndy5b0HFqSJjGlNYtzs=
        go.sum:     h1:d4KVXhMt913cLBEI/PXAy6ko+W7e9AhyAKBGh803qeE=
```

```
verifying github.com/ipfs/go-datastore@v0.0.1: checksum mismatch
        downloaded: h1:u3lrOIBAhGS5prBa94V89LJNMWlEsO2+zgFlEGTl0E4=
        go.sum:     h1:AW/KZCScnBWlSb5JbnEnLKFWXL224LBEh/9KXXOrUms=
```

gx publish 4.4.34