-
Notifications
You must be signed in to change notification settings - Fork 318
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
chore: fix RUSTSEC-2024-0370 proc-macro-error is unmaintained #1603
chore: fix RUSTSEC-2024-0370 proc-macro-error is unmaintained #1603
Conversation
I also wonder if this could become even simpler by adopting Examples Cargo Target. |
89bdffc
to
c32967b
Compare
I think I also found a bug in how the |
Also, it's something that we'd find out through #1018 if miniscript std/no-std weren't a blocker. |
51d8d64
to
8752555
Compare
I was testing the fixes and got it in 8752555, but I'll move it to a separate PR to make it easier to review (#1615). |
8752555
to
157d738
Compare
Rather than rename the example-crates can't we use the "exclude" key in the workspace Cargo.toml to exclude them from invocations of https://doc.rust-lang.org/cargo/reference/workspaces.html#the-members-and-exclude-fields |
I thought about it, but AFAICT it'll exclude from the workspace for any |
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.
After considering the options I don't see any downside to using this solution.
- add `blocking-https` as one of the default features, instead of `blocking-https-rustls`, they are basically the same in `esplora-client`. - add `async` and `blocking as required features for each test, using the `[[test]]` cargo target.
- add `use-rustls` as required features for `test_electrum.rs`, using the `[[test]]` cargo target approach.
157d738
to
2d43499
Compare
I rebased this one, as I updated the approach in #1615. |
dependency on `proc-macro-error`. In bitcoindevkit#1593 it's mentioned that `proc-macro-error` is unmaintained for the past few years, with no fix other than using proc-macro-error2 instead. As on our scenario it's merely a transitive dependency of `clap`, through `clap_derive` feature, which in latest releases doesn't depend on `proc-macro-error` we can just bump it to latest. It's valid to note that by bumping it, both examples that relies on clap are no longer MSRV (1.63) compliant.
2d43499
to
d802d00
Compare
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.
ACK d802d00
A candidate for fixing #1593. It builds on top of #1615
Description
In #1593 it's mentioned that
proc-macro-error
is unmaintained for thepast few years, with no fix other than using proc-macro-error2 instead.
As on our scenario it's merely a transitive dependency of
clap
,through
clap_derive
feature, which in latest releases doesn't depend onproc-macro-error
we can just bump it to latest.It's valid to note that by bumping it, both examples that relies on clap
are no longer MSRV (1.63) compliant.
That said, this PR does:
example_
prefix.Build & Test
CI job.Build & Test Example
CI job.clap
to4.5.17
.Notes to the reviewers
Changelog notice
example_
prefix.Build & Test
CI job.Build & Test Example
CI job.clap
to4.5.17
.Checklists
All Submissions:
cargo fmt
andcargo clippy
before committingBugfixes: