Skip to content

Fix rare issue concerning captures going stale on the AWS VPC CNI, as well as auto-resolve addresses with no currently seen DNS traffic in the cluster #125

Fix rare issue concerning captures going stale on the AWS VPC CNI, as well as auto-resolve addresses with no currently seen DNS traffic in the cluster

Fix rare issue concerning captures going stale on the AWS VPC CNI, as well as auto-resolve addresses with no currently seen DNS traffic in the cluster #125

Triggered via pull request September 18, 2024 21:04
Status Failure
Total duration 2m 35s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
vet
Process completed with exit code 1.
golangci-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/checkout@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/
vet
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/