GitLab

Rather than pushing errors back down to lower layers, propagate the
errors upward.

This commit adds a `ReceiveError` method to BitSwap's network receiver.

Still TODO: rm the error return value from:

    net.service.handler.HandleMessage

This is inspired by delegation patterns in found in the wild.

sending

true -> always send to peer

false -> use ledger-based strategy described in IPFS paper draft 3

fix(bitswap) pass go vet

fixes #97

https://github.com/jbenet/go-ipfs/issues/97

changing the bitswap interace breaks tests and makes things a bit
difficult going forward. I think I have a temporary solution to replace
the async method.

this commit partially reverts changes from:

ec50703395098f75946f0bad01816cc54ab18a58

https://github.com/jbenet/go-ipfs/commit/ec50703395098f75946f0bad01816cc54ab18a58

@perfmode using non-async version as apparently there's
a bug in async. will look into it.

@perfmode boom

test(bitswap) run synchronously to aid the scheduler

fix(bitswap) Put synchronously. Then notify async

to avoid letting client rely on order for correctness

misc:
* test network client getting more than max
* test for find providers
* rename factory method
* local network
* misc test improvements
* test bitswap get block timeout
* test provider exists but cannot connect to peer
* test sending a message async over local network

style(exch:bitswap) rename NetMessage adapter impl