-
Notifications
You must be signed in to change notification settings - Fork 113
Conversation
Fixed race condition via libp2p/go-mplex#41. Node.js/WebAssembly tests are still failing so I'll look into that next. |
Now CI is running into issues with other dependencies (looks like commit hashes that no longer exist). Pion is in the middle of renaming some things and gearing up for the release of v2. It'll probably get sorted out soon. In the meantime I can keep working on the failing Node.js/WebAssembly tests. |
IMO the code is complete enough for the first implementation of the core package. We're still missing a few things like the database storage layer and peer discovery, but a lot of this depends on other work that has yet to be done. Still WIP because of upstream dependency issues. The build currently fails with:
As well as some other errors that look like:
@fabioberger I don't think the code will change much if you want to go ahead and review. |
// TODO(albrow): We should be closing the host here. Unfortunately there is a | ||
// bug where the transport panics with "panic: close of closed channel". Needs | ||
// to be fixed upstream. | ||
// return n.host.Close() |
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.
Add a link to the issue/PR?
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.
Doesn't exist yet. I think it's faster to talk to the libp2p/go-libp2p-webrtc-direct
maintainer directly.
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.
Actually changed my mind. I might open an issue but for the moment development on the transport is blocked by pion/sctp#32 so it will be difficult to reproduce the error. See libp2p/go-libp2p-webrtc-direct#29 for some more context. I'll update this thread or mention it in Slack once an issue or PR is out.
Shoot. CI just failed on master (timed out) after this PR was merged. I suspect it may have to do with the same performance problems described in pion/sctp#32. Gonna revert for now. |
Most methods are stubbed for now. This just shows the interface and allows us to write some basic tests for
core.Node
which make use of the webrtc-direct transport.Go tests actually pass, but the race checker is being triggered by some low-level libp2p code. Will need to investigate further.
Wasm tests fail due to a timeout when trying to connect. I think this may have to do with incorrect/unusable port numbers being selected by Node.js.