You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, it might be best to just allow this warning. Since everything is working fine as it is. Alternatively we could try to use 'proc-macro-error2' instead, but that might cause new problems because it's not exactly the same as the old one.
If you agree with this, I'll submit a PR to add this warning to the allowlist for now.
Found a PR from another community that someone trying to replace it with 'proc-macro-error2': yewstack/yew#3752
Can we try proc-macro-error2? Unmaintained crate isn't the prefer one to rely on. If it is not trivial or causing too much breaking change, then we can consider adding a warning instead
As clap v3 is now out, and the structopt features are integrated into (almost as-is), structopt is now in maintenance mode: no new feature will be added.
As clap v3 is now out, and the structopt features are integrated into (almost as-is), structopt is now in maintenance mode: no new feature will be added.
Using proc-macro-error2 could introduce new issues that are tough to resolve, based on the PR I mentioned earlier. Since we got from their experience, I think we may try replace structopt with clap, I will start working on that
Activity
TDHSC commentedon Apr 3, 2025
take
TDHSC commentedon Apr 3, 2025
For now, it might be best to just allow this warning. Since everything is working fine as it is. Alternatively we could try to use 'proc-macro-error2' instead, but that might cause new problems because it's not exactly the same as the old one.
If you agree with this, I'll submit a PR to add this warning to the allowlist for now.
Found a PR from another community that someone trying to replace it with 'proc-macro-error2': yewstack/yew#3752
jayzhan211 commentedon Apr 4, 2025
Can we try
proc-macro-error2? Unmaintained crate isn't the prefer one to rely on. If it is not trivial or causing too much breaking change, then we can consider adding a warning insteadalamb commentedon Apr 4, 2025
Another approach would be to remove the use of
structoptin datafusion benchmarks (and update them to use clap directly...)While more work this would likely be an easier to maintain long term solution
https://crates.io/crates/structopt
The docs page basically says it is in maintenance mode; https://docs.rs/structopt/0.3.26/structopt/#maintenance
TDHSC commentedon Apr 4, 2025
Using
proc-macro-error2could introduce new issues that are tough to resolve, based on the PR I mentioned earlier. Since we got from their experience, I think we may try replacestructoptwithclap, I will start working on that[-]`cargo audit` is failing on main[/-][+]`security_audit` CI check is failing on main[/+]alamb commentedon Apr 7, 2025
I agree that removing structopt is the best approach
To fix the CI check, perhaps we can temporarily ignore that warning as it relates to a tool that is not published as part of DataFusion
TDHSC commentedon Apr 7, 2025
Great, I will go ahead submit a PR to ignore it first
alamb commentedon Apr 7, 2025
Thank you so much @Jiashu-Hu