Skip to content

aa: make lint cover all workspace packages under attestation-agent - #1652

Open
Xynnn007 wants to merge 1 commit into
confidential-containers:mainfrom
Xynnn007:ci-bin-linter
Open

aa: make lint cover all workspace packages under attestation-agent#1652
Xynnn007 wants to merge 1 commit into
confidential-containers:mainfrom
Xynnn007:ci-bin-linter

Conversation

@Xynnn007

Copy link
Copy Markdown
Member

Previously make lint only clippy'd the attestation-agent crate, so sibling crates (notably attester's evidence_getter via bin) were never linted. Clippy each package with -D warnings, and use --all-targets plus bin where binaries exist.

Note that sev parts are also included as they are in tree. I will make a separate PR to get rid of them altogether.

Previously make lint only clippy'd the attestation-agent crate, so
sibling crates (notably attester's evidence_getter via bin) were never
linted. Clippy each package with -D warnings, and use --all-targets plus
bin where binaries exist.

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@Xynnn007
Xynnn007 requested a review from a team as a code owner August 11, 2026 09:38

@fitzthum fitzthum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a good way to just check all the packages? Maybe cargo clippy --all? This seems a little fragile as-is.

@mythi

mythi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Clippy each package with -D warnings, and use --all-targets plus bin where binaries exist.

I wonder if cargo clippy --workspace --all-targets -- -D warnings would be sufficient?

@Xynnn007

Copy link
Copy Markdown
Member Author

The Makefile now is under attestation-agent directory, thus as blackbox it's proper for it to only cover crates under the attestation-agent/*.

There are two ways to fix original issue

  1. get this merged and improve clippy coverage ASAP and let's refactor the messy CI code in the repo
  2. refactor the messy CI code in the repo, including Makefiles

I prefer 1, to resolve things asap and let's do "make it better" work then.

@mythi

mythi commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

my 2 cents is that the coverage gap is not critical enough that it cannot wait proper refactoring.

@fitzthum fitzthum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I am fine with this in the short term. From the CI perspective, we don't really need to lint the components individually. It shouldn't take too much of a refactor to just lint the entire workspace instead. I guess we might want to keep this Make target around tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants