feat: add unit tests for CNS endpoint handler APIs #91
behzad-mirgovulncheck.yaml
on: pull_request
Check all go.mod files are in matrix
3s
Matrix: govulncheck
Annotations
37 errors and 42 warnings
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Process completed with exit code 1.
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/cmd/ipv6-hp-bpf/main.go#L83
undefined: ingress.LoadIngressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/cmd/ipv6-hp-bpf/main.go#L82
undefined: ingress.IngressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/cmd/ipv6-hp-bpf/main.go#L73
undefined: egress.LoadEgressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/cmd/ipv6-hp-bpf/main.go#L71
undefined: egress.EgressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/pkg/ingress/ingress.go#L11
undefined: IngressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf):
bpf-prog/ipv6-hp-bpf/pkg/egress/egress.go#L11
undefined: EgressObjects
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (.)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
|
|
Run govulncheck (cilium-log-collector)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (cilium-log-collector)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>02UvZaQAAAADuovX9Llt2T5eCOETcos0RQ0hJMzBFREdFMDQxMQBFZGdl
|
|
Run govulncheck (cilium-log-collector)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (cilium-log-collector)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (zapai)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (zapai)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03EvZaQAAAACrX6AJCTKLRoXcil6n/J8FUEhMMzBFREdFMDExOQBFZGdl
|
|
Run govulncheck (zapai)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (zapai)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (dropgz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (dropgz)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03UvZaQAAAAC6spCm21LVSqV/eixEKeqbUEhMMzBFREdFMDIxOQBFZGdl
|
|
Run govulncheck (dropgz)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (dropgz)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (pkgerrlint)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (pkgerrlint)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03kvZaQAAAABkR9Dgko47TYgcPzPdYvMMUEhMMzBFREdFMDQxNABFZGdl
|
|
Run govulncheck (pkgerrlint)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (pkgerrlint)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (azure-ip-masq-merger)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (azure-ip-masq-merger)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03kvZaQAAAADqKU+aVxrISY7yg9jZie4/UEhMMzBFREdFMDExMQBFZGdl
|
|
Run govulncheck (azure-ip-masq-merger)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (azure-ip-masq-merger)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (tools/azure-npm-to-cilium-validator)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (tools/azure-npm-to-cilium-validator)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06UvZaQAAAACNOMkdqnp7Q7eu/pyq3oLyUEFPRURHRTA1MDkARWRnZQ==
|
|
Run govulncheck (tools/azure-npm-to-cilium-validator)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (tools/azure-npm-to-cilium-validator)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (azure-ipam)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (azure-ipam)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06kvZaQAAAAD6Y9/GzlbAQbIJjU4RBwthUEFPRURHRTA2MTAARWRnZQ==
|
|
Run govulncheck (azure-ipam)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (azure-ipam)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
Run govulncheck (.)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (.)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0BEzZaQAAAAA8t04sQ/TNSrqEhWkhnMxiUEhMMzBFREdFMDIxMgBFZGdl
|
|
Run govulncheck (.)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (.)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (.)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
Run govulncheck (azure-iptables-monitor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run govulncheck (azure-iptables-monitor)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0FkzZaQAAAABd02qBeuASS4iberJQz0QsUEFPRURHRTA1MTEARWRnZQ==
|
|
Run govulncheck (azure-iptables-monitor)
Failed to restore: Cache service responded with 400
|
|
Run govulncheck (azure-iptables-monitor)
Both go-version and go-version-file inputs are specified, only go-version will be used
|
|
Run govulncheck (azure-iptables-monitor)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|