Replies: 1 comment 1 reply
-
Did you see your Peer ID printed? Like
Which means the signal will only be captured once before entering main loop, not during execution. It also causes
Also if you want to explore rust-libp2p with GUI, check out my little project #6014 🌟 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've opened an issue for the rust implementation of the universal connectivity on the repo, 3 weeks ago.
Apart from that, which highlights a component
signal_hook::iterator::Signals
, not available on Windows.I've also encountered many problems when trying to bootstrap with the official
IPFS_BOOTSTRAP_NODES
.Other implementation of the universal connectivity work, like the go example. But for the rust example it does not.
Is it just a Windows problem? Or is it a known problem?
What I did:
tokio::signal::windows
instead ofsignal_hook::iterator::Signals
. I explain this part better on the previously mentioned issue.cargo run
on my PC, and open chrome and go to the site universal-connectivity.on-fleek.app the two instances do not recognize/connect to each other. (If I've understood correctly this should not be the case)I'm a noob when it come to rust, so it is entirely possible that I made some kind of mistake. Let me know if it's a problem that happens only to me, or if others have the same problem.
As a Side Note
Is there a basic DHT rust-example for Node-Discovery.
I tried with the
.start_providing
and.get_providers
methods but to no avail, I then tried to study the universal-connectivity repo, and encountered this problem.Beta Was this translation helpful? Give feedback.
All reactions