static-check

For testing Purpose #881

Sign in to view logs

Triggered via pull request March 4, 2025 07:55

synchronize #5097

resource/parse-test

Status Failure

Total duration 2m 2s

Artifacts –

static-check.yml

on: pull_request

staticcheck (project)

Annotations

10 errors

staticcheck (project): agent/check_handler.go#L218

printf-style function with dynamic format string and no further arguments should use print-style function instead (SA1006)

staticcheck (project): agent/check_handler.go#L253

printf-style function with dynamic format string and no further arguments should use print-style function instead (SA1006)

staticcheck (project): agent/check_handler.go#L259

printf-style function with dynamic format string and no further arguments should use print-style function instead (SA1006)

staticcheck (project): agent/check_handler.go#L265

printf-style function with dynamic format string and no further arguments should use print-style function instead (SA1006)

staticcheck (project): backend/api/authentication_test.go#L38

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)

staticcheck (project): backend/api/authentication_test.go#L39

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)

staticcheck (project): backend/apid/routers/authentication.go#L54

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)

staticcheck (project): backend/apid/routers/authentication.go#L55

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)

staticcheck (project): backend/apid/routers/authentication.go#L117

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)

staticcheck (project): backend/apid/routers/authentication.go#L118

should not use built-in type string as key for value; define your own type to avoid collisions (SA1029)