-
Notifications
You must be signed in to change notification settings - Fork 5
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
Where should I create an issue related to the rs-ipfs substrate fork? #2
Comments
A little update on the aforementioned issue: I was able to play with the options so that the embedded IPFS nodes are reachable externally: // client/offchain/src/lib.rs
options.listening_addrs = vec!["/ip4/0.0.0.0/tcp/0".parse().unwrap()]; However I'm still facing two difficulties:
|
Thank you for your patience here. I have re-enabled issues at https://github.com/rs-ipfs/substrate 👍 |
Also, for your convenience, I transferred this issue for you :) pinging @ljedrz |
Thanks @aphelionz for the update and the transfer. Update on my side: having issues with the But I'll be more than willing to move forward with the |
I see that the issue with connecting to the outside world is resolved, nice; as for the other listed issues:
|
Here's the setup:
Here's the error:
|
This looks like some bug between |
It is taking a while to upgrade because of the dependencies churn, work continues on rs-ipfs/rust-ipfs#446. |
Hi,
Although the offchain-ipfs manual stipulates I should create an issue on the
substrate
fork repo if needed, such feature seems to be deactivated on the aforementioned repository.Where should I create such an issue?
PS: the issue is that the IPFS node embedded by the offchain worker seems to not be exposed to the external world => I cannot locally curl it, it doesn't connect to any peers, etc.
Thanks!
The text was updated successfully, but these errors were encountered: