fix(config): [global] and [docker] unknown-key warnings carry 'did you mean?' (#678) #1617
CybotTMci.yml
on: pull_request
go-check
/
Build & Test
1m 56s
go-check
/
golangci-lint
1m 43s
go-check
/
govulncheck
31s
go-check
/
gosec
1m 26s
go-check
/
Smoke Tests (fast feedback)
1m 11s
go-check
/
Fuzz (corpus replay)
40s
go-check
/
License Scan
28s
go-check
/
Integration Tests
1m 41s
go-check
/
E2E Tests
1m 11s
Annotations
10 errors and 1 warning
|
go-check / govulncheck
docker.ExecServiceAdapter.Create calls client.Client.ContainerExecCreate
|
|
go-check / govulncheck
docker.ExecServiceAdapter.Start calls client.Client.ContainerExecAttach
|
|
go-check / govulncheck
docker.ContainerServiceAdapter.Create calls client.Client.ContainerCreate
|
|
go-check / govulncheck
docker.ContainerServiceAdapter.Attach calls client.Client.ContainerAttach
|
|
go-check / govulncheck
docker.Client.Close calls client.Client.Close
|
|
go-check / govulncheck
middlewares.PresetLoader.loadFromURL calls http.Client.Do, which eventually calls client.CheckRedirect
|
|
go-check / govulncheck
docker.init calls client.init, which calls checkpoint.init
|
|
go-check / govulncheck
docker.init calls client.init, which calls build.init
|
|
go-check / govulncheck
docker.init calls container.init, which calls blkiodev.init
|
|
go-check / govulncheck
docker.init calls client.init, which calls api.init
|
|
go-check / govulncheck
govulncheck reported vulnerabilities (exit 1). Non-blocking because govulncheck-strict=false; track as follow-up.
|