Skip to content
lint

Add support for Linkerd enforcement through ClientIntents #194

Sign in to view logs

Add support for Linkerd enforcement through ClientIntents

Add support for Linkerd enforcement through ClientIntents #194

Triggered via pull request November 5, 2024 15:00
@evyatarmegedevyatarmeged
synchronize #504
evya/linkerd_to_operator_latest
Status Failure
Total duration 2m 11s
Artifacts –

lint.yml

on: pull_request
vet
1m 58s
vet
golangci
1m 21s
golangci
Check for Markdown errors
47s
Check for Markdown errors
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 3 warnings
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
golangci
Cannot open: File exists
vet
undefined: linkerdserver
vet
github.com/sirupsen/logrus.Warning call has possible Printf formatting directive %s
vet
github.com/sirupsen/logrus.Warning call has possible Printf formatting directive %s
vet
Process completed with exit code 1.
golangci
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
golangci
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
vet
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/