namesys/pubsub: pubsub Publisher and Resolver

[vyzo]

Implements a namesys publisher and resolver with pubsub.

[vyzo]

Forced pushed the last commit to restart jenkins -- errored out with some system-specific gremlin.
Rebased on master.

[vyzo]

Updated for changes in the command interface.

[vyzo]

it's not clear why jenkins failed -- all the not ok's are marked as known breakages.
I also can't restart the build through the interface for some reason.

[keks]

@vyzo I restarted both the broken travis build and the jenkins build. Both fail, but at different places.

Travis:
in test/sharness/t0183-namesys-pubsub.sh

expecting success: 
    echo -n "" > expected &&
    ipfsi 1 name pubsub subs > subs1 &&
    ipfsi 2 name pubsub subs > subs2 &&
    test_cmp expected subs1 &&
    test_cmp expected subs2

> diff -u expected subs1
--- expected	2017-11-19 13:20:38.000000000 +0000
+++ subs1	2017-11-19 13:20:38.000000000 +0000
@@ -1 +0,0 @@
--n 

not ok 18 - check subscriptions

It looks like echo -n prints -n on the Travis Mac builders.

Jenkins:
in test/sharness/t0088-repo-stat-symlink.sh

expecting success: 
  export IPFS_PATH="sym_link_target" &&
  reposize_direct=$(ipfs repo stat | grep RepoSize | awk '{ print $2 }') &&
  export IPFS_PATH=".ipfs" &&
  reposize_symlink=$(ipfs repo stat | grep RepoSize | awk '{ print $2 }') &&
  test $reposize_symlink -ge $reposize_direct

not ok 4 - 'ipfs repo stat' RepoSize is correct with sym link

[vyzo]

It looks like echo -n prints -n on the Travis Mac builders.

wow, that's very unfortunate. I wonder if there is a version of echo that works correctly, otherwise i'll have to use touch with a unique filename.

in test/sharness/t0088-repo-stat-symlink.sh

that's completely unrelated to this PR.

[vyzo]

Changed the sharness test to use rm && touch instead of echo -n.

[vyzo]

Another jenkins failure, similar to the first one -- all the not ok are in known breakage.
What's up with our jenkins setup, why is it being flaky?

[vyzo]

note that circle and travis were successful.
@keks can you give jenkins another restart to see if the pattern repeats?

[whyrusleeping]

@vyzo we use printf instead of echo -n generally. Its the most cross platform thing i've found

[whyrusleeping]

@Stebalien could you check out the gx deps here? I think that the go-testutil dep is a bit wonky (other things are importing the old go-testutil)

[Stebalien]

Dammit. I did not mean to update that package. Let's try this again from the bottom.

[Stebalien]

On the bright side, #4403 should fix that issue. Of course, it'll probably introduce a bunch of ever so fun merge conflicts.

[whyrusleeping]

I squashed and rebased, the dependency issues should be fixed now

[whyrusleeping]

Strange ipns related failure on jenkins, copied the failure logs here: https://gist.github.com/whyrusleeping/9f4bef1726577e14a67568b9cd997f5a

Any chance this is related to the pubsub changes @vyzo ?

cc @Stebalien as maybe this is a known random failure.

[vyzo]

the tests seem to have a 300ms timeout -- maybe that's the cause?
I haven't seen this failing before, but normal ipns resolution shouldn't be affected

[vyzo]

@whyrusleeping can you rerun jenkins to see if the problem is persistent?
it might be something post squash, or it might be a gremlin (or simply 300ms not being enough). I still don't have rebuild permissions on jenkins.

[whyrusleeping]

@victorbjelkholm can you trigger this one to be rebuilt? And also tell me how to do it myself?