You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linter errors exist on #1417 because of problems with how we're doing golangci-lint.
Our golangci-lint is using cached info.
look what happens when golangci-lint is run locally:
golangci-lint run ./...
WARN [runner] The linter 'golint' is deprecated (since v1.41.0) due to: The repository of the linter has been archived by the owner. Replaced by revive.
WARN [runner] The linter 'interfacer' is deprecated (since v1.38.0) due to: The repository of the linter has been archived by the owner.
WARN [runner] The linter 'maligned' is deprecated (since v1.38.0) due to: The repository of the linter has been archived by the owner. Replaced by govet 'fieldalignment'.
WARN [runner] The linter 'scopelint' is deprecated (since v1.39.0) due to: The repository of the linter has been deprecated by the owner. Replaced by exportloopref.
That is, other than warnings, it returns zero. If it returns zero, then the PR #1417 is completely fine. It returns zero. I'll fix the caching in v6.
Here's the main branch at the current commit height:
((67fbb896…))> golangci-lint run ./...
WARN [runner] The linter 'interfacer' is deprecated (since v1.38.0) due to: The repository of the linter has been archived by the owner.
WARN [runner] The linter 'maligned' is deprecated (since v1.38.0) due to: The repository of the linter has been archived by the owner. Replaced by govet 'fieldalignment'.
WARN [runner] The linter 'scopelint' is deprecated (since v1.39.0) due to: The repository of the linter has been deprecated by the owner. Replaced by exportloopref.
WARN [runner] The linter 'golint' is deprecated (since v1.41.0) due to: The repository of the linter has been archived by the owner. Replaced by revive.
Summary of Bug
Linter errors exist on #1417 because of problems with how we're doing golangci-lint.
Our golangci-lint is using cached info.
look what happens when golangci-lint is run locally:
That is, other than warnings, it returns zero. If it returns zero, then the PR #1417 is completely fine. It returns zero. I'll fix the caching in v6.
Here's the main branch at the current commit height:
Same thing.
Closed by: #1507
Version
any
Steps to Reproduce
golangci-lint run ./...
For Admin Use
The text was updated successfully, but these errors were encountered: