Skip to content

TEST_STATIC

TEST_STATIC #876

Triggered via pull request March 3, 2025 11:24
Status Failure
Total duration 1m 47s
Artifacts

static-check.yml

on: pull_request
staticcheck (project)
1m 38s
staticcheck (project)
Fit to window
Zoom out
Zoom in

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)