* Do not use golangci action for better reproducibility
* Add fix to trigger build
* Fix all reported issues
* fix more lint errors
* Add missing import
* Remove unused method
* Remove change not necessary
This solves #5679 , and also implements #5515, #5509 and lays the ground for #5516
With the introduction of Wrap, Is and As in the standard library, we've now got built-in support for wrapping.
On top of that, a common pattern in the community is to define errors tailored to the context of each project while still conforming to the error and Unwrap interfaces (see Upspin, Chromium)
The output now includes stack traces and additional info
* Adding gosec linter
Adding gosec (Static application security testing) linter.
* Testing gosec exclusion in golangci-lint
G110 is being triggered - testing if exclude works, then will revert and leave the excludes section there for future needs.
Also adding some tests to exclude rules
* Update .golangci.yml
Testing gosec allow list of rules
* Update .golangci.yml
Trying gosec deny list of rules
* Update .golangci.yml
Reconfiguring G306 alert to use 644, less stringent, and adding every file with current warnings to exclusions. Once this is all buttoned up and running on NEW files, we will go back and address all issues or put a comment stating why the file is excluded here.
* Update .golangci.yml
Removing exclusion to see if lint now fails
* Update .golangci.yml
Removing most exclusions to test
* Update .golangci.yml
Removing 100% of exclusions for more testing
* Update .golangci.yml
Re-adding exclusions slowly and testing to be sure we only exclude what is needed
* Update .golangci.yml
Adding all exclusions and comments per category pointing to github issues for investigating and cleaning up over time.
Add a relatively minimal set of linters that raise safe and
mostly un-opinionated issues with the code. It runs
automatically on CI via a github action.
