Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Conversation

daviddias
Copy link
Member

No description provided.

@daviddias
Copy link
Member Author

@dignifiedquire still same bug. It is because browser nodes are getting websockets addr, which they shouldn't. This also should not be a issue cause the transport for websockets is just added after the listen, but this errors comes with the fact that you goOnline and goOffline several times.

See: https://github.com/ipfs/js-libp2p-ipfs-browser/blob/master/src/index.js#L36-L44

Adding ws multiaddrs to browser nodes is confusing, it already misguided @haadcode twice and will mislead our users (remember that those websockets addrs get transferred through identify). Would you mind if we change that from the tests?

@dignifiedquire
Copy link
Member

Would you mind if we change that from the tests?

No, just make sure they are added when running in node where we need them

@daviddias daviddias force-pushed the update-deps2 branch 3 times, most recently from 1fdc93a to a2529fb Compare May 27, 2016 14:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants