Skip to content

tests/screentest: add test for vuln with custom_ranges #203

tests/screentest: add test for vuln with custom_ranges

tests/screentest: add test for vuln with custom_ranges #203

Triggered via push July 15, 2024 15:19
Status Failure
Total duration 57s
Artifacts

govulncheck.yml

on: push
govulncheck
48s
govulncheck
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
govulncheck
gcpqueue.gcp.ScheduleFetch calls apiv2.Client.CreateTask, which eventually calls json.Decoder.Peek
govulncheck
gcpqueue.gcp.ScheduleFetch calls apiv2.Client.CreateTask, which eventually calls json.Decoder.Read
govulncheck
gcpqueue.gcp.ScheduleFetch calls apiv2.Client.CreateTask, which eventually calls protojson.Unmarshal
govulncheck
database.wrapConn.QueryContext calls ocsql.ocConn.QueryContext, which eventually calls pgproto3.Bind.Encode
govulncheck
database.copy calls pgx.Conn.CopyFrom, which eventually calls pgproto3.CopyDone.Encode
govulncheck
database.copy calls pgx.Conn.CopyFrom, which eventually calls pgproto3.CopyFail.Encode
govulncheck
database.wrapConn.QueryContext calls ocsql.ocConn.QueryContext, which eventually calls pgproto3.Describe.Encode
govulncheck
database.wrapConn.QueryContext calls ocsql.ocConn.QueryContext, which eventually calls pgproto3.Execute.Encode
govulncheck
database.wrapConn.QueryContext calls ocsql.ocConn.QueryContext, which eventually calls pgproto3.Parse.Encode
govulncheck
database.wrapOCDriver.Open calls stdlib.Driver.Open, which eventually calls pgproto3.PasswordMessage.Encode
govulncheck
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/