Bubble upstream the latest changes on libp2p #287
Conversation
daviddias
force-pushed
the
test/network-turbulence
branch
5 times, most recently
from
ca50885 to
d8cd44d
Compare
|
Node.js tests work like a charm, however, the browser tests fails on the dial (no available transports), this typically means that the listener didn't start or that the dialer doesn't have the required transport. @haadcode mentioned that libp2p-ipfs-browser is not being injected properly and after a few attempts playing with .aegir.js, I didn't manage to have a success confirming this. @dignifiedquire can you shine some light of Webpack goodness into this PR? :) |
daviddias
force-pushed
the
test/network-turbulence
branch
3 times, most recently
from
6b4854e to
c3a543f
Compare
|
@dignifiedquire nevermind, all good now :) |
| "gulp": "^3.9.1", | ||
| "idb-plus-blob-store": "^1.1.2", | ||
| "interface-ipfs-core": "^0.1.5", | ||
| "left-pad": "^1.1.0", |
There was a problem hiding this comment.
are you sure you want to use this module :D
There was a problem hiding this comment.
ahaha I was waiting for someone to catch this :D
daviddias
force-pushed
the
test/network-turbulence
branch
from
c3a543f to
011ea47
Compare
|
@dignifiedquire any other comments? Good to merge and continue tackling on more tests in more PR (this was about making libp2p robustness tests, but then it became more about making libp2p-ipfs more powerful and fix a bunch of bugs along the way) |
|
go for it, I think we ahoul encapaulate even more in libp2p that we are doing currently in js-ipfs but that can come later |
3 participants
Uh oh!
There was an error while loading. Please reload this page.