-
Notifications
You must be signed in to change notification settings - Fork 957
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
feat: Better error reporting when features are disabled #2972
Conversation
This TODO can be resolved now.
Having an entire module for one struct doesn't quite cut it.
This should make for better error messages when support for certain keys is disabled. Fixes #2971.
This leads to double printing of errors when iterating the source chain.
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.
As always, great work. Thank you for tackling this so thoroughly. Thanks for breaking it up into smaller meaningful commits.
@mxinden test-plan doesn't seem to be happy :( https://github.com/libp2p/rust-libp2p/actions/runs/3186899238/jobs/5197936812 |
CI is failing with:
I would like to test this with a fresh |
I should have included this in #2931 but I forgot. Can you update the pull request now that |
Updates dependency. In the hope to resolve conflict from libp2p/rust-libp2p#2972.
Updates dependency. In the hope to resolve conflict from libp2p/rust-libp2p#2972.
We only need this if one of these is not enabled, i.e. they are `not(all)` enabled.
By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as libp2p/rust-libp2p#2972.
@thomaseizinger libp2p/test-plans#72 is merged. Can you update this pull request? |
This pull request has merge conflicts. Could you please resolve them @thomaseizinger? 🙏 |
This is now released and available on crates.io.
This reverts commit cedd5a1.
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.
👍
Here we go! |
🎉 |
Description
In case support for e.g. RSA keys is disabled at compile-time, we will now print a better error message. For example:
Fixes #2971.
Links to any relevant issues
Depends-On: #3081
Open Questions
Change checklist