-
Notifications
You must be signed in to change notification settings - Fork 4
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
Updates to get the example in the README.md working #2
base: master
Are you sure you want to change the base?
Conversation
This dir does not exist so `cargo` would fail on every command.
The usage within the library was not compatible with the version listed in Cargo.toml. So I updated, and reworked the code to the current Clap
I'm new to codebase so I don't feel comfortable removing these yet
Please enter the commit message for your changes. Lines starting
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.
Looks reasonable, good to have the example to at least work before doing anything else. Is the idea to upgrade hypercore-protocol to latest master eventually?
@ttiurani That is the plan! I'd like to use some of the functionality in here (in |
These changes were needed to get the example in the
README.md
working, and to silence existing warnings. There was only one existing test, and it passes.The only thing that may be controversial here are these two places where I've patched dependencies, and point to my own fork. This is intended to be a temporary solution. The practice is common within this repo. User @Frando own several of these branches, but he is a more well known community member 😉.
libutp-sys
which I made to fix a build failure inbindgen
.hypercore-protocol-rs v3.1
However building this version is now broken because of it's dependency onsnow v0.7.0-alpha5
which causes a build failure. The branch this now points to contains this patch which bumps the snow version to one that works (0.8
). I would like to merge this upstream but thehypercore-protocol-rs
repository does not have a3.1
tag or branch which I could make a PR against. A different fix could be bumping thehypercore-protocol-rs
version itself. I'm looking into this.