Skip to content

refactor(core,server): make commands not rely on server context #66143

refactor(core,server): make commands not rely on server context

refactor(core,server): make commands not rely on server context #66143

Triggered via pull request May 20, 2024 09:12
Status Failure
Total duration 3m 57s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
golangci-lint: x/genutil/client/testutil/helpers.go#L27
Error return value is not checked (errcheck)
golangci-lint: testutil/network/util.go#L174
Error return value of `genutiltest.TrackConfig` is not checked (errcheck)
golangci-lint: x/genutil/client/cli/init_test.go#L383
Error return value of `genutiltest.WriteAndTrackConfig` is not checked (errcheck)
golangci-lint: server/cmd/execute.go#L46
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: server/cmd/execute.go#L47
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: x/genutil/client/testutil/helpers.go#L35
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: x/genutil/client/testutil/helpers.go#L36
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: server/util.go#L191
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: server/util.go#L192
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint: server/util_test.go#L65
SA1029: should not use built-in type string as key for value; define your own type to avoid collisions (staticcheck)
golangci-lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: technote-space/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.