-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[WIP] Move to pull-streams #440
Conversation
85c5309
to
a5bc23b
Compare
It looks like the swarm tests are not passing due to secio. Next step, test secio better and fix any issues with it + interop with go. |
I finally have the swarm tests passing. It seems there is something strange going on on the connection between nodes which results in the bitwap tests not passing. Other than those, only some smaller details in the |
bitswap tests pass with all new bug fixes in place :) |
@dignifiedquire so, it is only missing the files tests? :D |
"pull-file": "^0.5.0", | ||
"pull-paramap": "^1.1.6", | ||
"pull-stream": "^3.4.3", | ||
"pull-stream-to-stream": "^1.3.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Let's make sure to update it to latest
pretty much only a single file test is failing at this point. Which is only due to the to node stream conversions |
@dignifiedquire could you describe it more? |
The get directory test fails due to the content stream of one nested file not ending properly for some reason. I haven't tracked down where exactly it is failing. |
With the latest version I finally have them file tests passing when using pull-stream/pull-stream-to-stream#5 |
All tests passing locally with ipfs-inactive/interface-js-ipfs-core#70 🎉 |
Go-ipfs now normalizes paths before adding files. This will: * remove any leading slashes. * remove any `/./` components. * normalize any `/../` components. That breaks this test which assumes that paths are returned _exactly_ as specified.
test/go-ipfs-repo
to the latest version of go-ipfs.Tests Passing
Ref #403