GitLab

until construction is complete on the actual async method

reverts changes from ec50703395098f75946f0bad01816cc54ab18a58

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

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

@jbenet

Handshake library has been modified to use Secure Pipe. This test
targets the old implementation.

TODO: write a new handshake test

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

@perfmode boom

There are (so far) two sorts of addresses that peers care about:

- peer network addresses, local to listen, saved to bootstrap.
  `config.Identity.Address`

- peer RPC network address, local RPC tcp endpoint
  `config.RPCAddress`

@whyrusleeping @perfmode

In the future, let's have a (signed) list of bootstrap
nodes. Ideally just a list of ipfs multiaddrs (with node.ID)

for now, ipfs add output format:

    added <hash> <path>
    ...

(these commands will adhere to strict formats.)

let's keep this a turn-on for testing sort of thing.
(want the outputs of commands like `ipfs add` to be
usable as inputs to other programs/scripts).

maybe we should consider adding a --debug (not -d),
once we figure out adding flags that apply globally :)
@whyrusleeping

(perhaps should be logged instead)

test(bitswap) run synchronously to aid the scheduler

fix(bitswap) Put synchronously. Then notify async

to avoid letting client rely on order for correctness