-
Notifications
You must be signed in to change notification settings - Fork 139
Clippy updates #672
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
base: main
Are you sure you want to change the base?
Clippy updates #672
Conversation
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.
Thanks @marosset! This and the follow-up to move it to a different workflow and reduce CI time will be great to have :)
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.
This looks good overall. I have left inline a bunch of opinionated tips for defensive shell coding, which mostly don't matter here due to the fact that cargo features have a fairly limited character set. Feel free to ignore them, but I thought you might find them interesting/useful---unless otherwise noted, the style that I suggest generally deals nicely with pretty much any special characters in names of things by being careful to control quoting and word splitting. The one exception is NULs, which cannot be dealt with in bash unless you go to a great deal of effort to never read anything into a bash string (which is at heart a C string, and can't contain NULs).
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.
Again, feel free to ignore shell style nits
It looks like some more clippy issues got introduced by #696 |
Signed-off-by: Mark Rossett <[email protected]>
@syntactically - Can you review the new updates I pushed (50b08fe) which fixes some clippy issues in hyperlight_guest_bin introduced by a recent PR? |
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.
LGTM, ignoring any potential bash hygiene issues.
Btw, if mshv3 is a required feature, will mshv2 ever be checked? Since mshv3 "overwrites" mshv2
I think we are planning to get rid of mshv2 very shortly. |
job Signed-off-by: Mark Rossett <[email protected]>
Signed-off-by: Mark Rossett <[email protected]>
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.
Thanks for catching these! Sorry, I guess our previous clippy configuration was missing this crate & I didn't think to run it manually. I have a bunch of comments on the safety notes; I can also do a commit to write them myself if you would like.
No problem. I think I addressed all the comments. PTAL |
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.
These look much better, thanks! Commented on a few typos I saw but other than that looks good :)
/sigh, let me fix those |
Signed-off-by: Mark Rossett <[email protected]>
Fixes #549
WIP - I plan to move the clippy and fmt check out of
dep_rust
so we can a) run the in parallel, and b) not need to run them for each arch/hypervisor/target matrix. Right now I just want to test that we've caught all the clippy issues