-
Notifications
You must be signed in to change notification settings - Fork 678
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
Add clarity and libsigner to clippy CI and fix all clippy warnings #5592
Conversation
Signed-off-by: Jacinta Ferrant <[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.
LGTM! Man, some of the stuff clippy can do is pretty amazing
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[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.
Looks good, lots of little improvements here. I left some suggestions and personally I don't think ClarityName::from()
on a constant value is a problem, but others might take issue with it
Signed-off-by: Jacinta Ferrant <[email protected]>
…anup Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[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.
Just one minor comment, but approved again
… into feat/clippy-ci
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 getting this done!
We do this as part of our release process already, but I just want to overcommunicate that we will want to do a chain replay before releasing this. There has been a case in the past where a Clippy PR had accidentally introduced a consensus bug (it turned out that git itself didn't merge it correctly, but the code still compiled).
Looking into why CI passes but then when attempt to merge...stacks core unit tests are failing. Checked out develop and the following three tests are failing there:
|
… into feat/clippy-ci
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
No description provided.