Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with latest secio + two versions of peer-ids #2

Open
mkg20001 opened this issue Jul 18, 2019 · 1 comment
Open

Problems with latest secio + two versions of peer-ids #2

mkg20001 opened this issue Jul 18, 2019 · 1 comment

Comments

@mkg20001
Copy link
Owner

Basically we now have two versions of peer-id: The async/await based and the callback based

The problem is that instances created with the newer version get passed to a libp2p swarm (specifically secio) that expects the async apis to be using callbacks, not promises.
So it dies whenever it tries to do a secio handshake, gets stuck at 3 - writing exchange

@mkg20001
Copy link
Owner Author

Trying to maybe resolve the disaster using libp2p/js-libp2p-secio#108
But chances are high this will just make it explode even more

So let's wait until libp2p is fully async/await or something ™️ happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant