GitLab

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

It's impossible to find the self ID in the DHT because of this statement https://github.com/libp2p/go-libp2p-kad-dht/blob/ac6772539b80d687c8ed711024b104aaa881c1d6/handlers.go#L257
So maybe we should ignore the "not found" error in this case, like we do it for the random walk.

defer dialqueue action until initial peers have been added

When a peer is found, add its addr to the peerstore, just like the addresses for closer peers are added. In particular this is helpful for followup queries by the DHT user.

gx publish 4.4.33

gomod: update go-libp2p

We usually _explicitly_ call connect before calling `prep` but we may disconnect
somewhere in-between. We _don't_ want to get stuck here dialing if the context
has been canceled.

gx publish 4.4.32

* Add IpfsDHT.{Bootstrap{Random,Self},Peer{Id,Key}}
* Include client mode tests, support for Ping, and uncruft setupDHTs
* Include xerrors in deps

refresh go mod // tag v0.0.3

Fix travis build

fix(dialQueue): account for failed dials

gx publish 4.4.30