Skip to content
trivy-fs

Allow configuring all ConnTrackers' debug trace level at runtime (#2023) #2966

Sign in to view logs

Allow configuring all ConnTrackers' debug trace level at runtime (#2023)

Allow configuring all ConnTrackers' debug trace level at runtime (#2023) #2966

Triggered via push September 16, 2024 23:25
@ddelnanoddelnano
pushed 2704ade
main
Status Success
Total duration 44s
Artifacts –

trivy_fs.yaml

on: push
code-scan
35s
code-scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
src/stirling/source_connectors/socket_tracer/cql_trace_bpf_test ► src/stirling/source_connectors/socket_tracer/cql_trace_bpf_test: bazel-testlogs/src/stirling/source_connectors/socket_tracer/cql_trace_bpf_test/test.xml#L0
Failed test found in: bazel-testlogs/src/stirling/source_connectors/socket_tracer/cql_trace_bpf_test/test.xml Error: Test failed
code-scan
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@8f4b7f84864484a7bf31766abe9204da3cbe65b3, github/codeql-action/upload-sarif@04df1262e6247151b5ac09cd2c303ac36ad3f62b. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/