prysm-pulse/tools/analyzers
Preston Van Loon c1197d7881
Add static analysis for unsafe uint casting (#10318)
* Add static analysis for unsafe uint casting

* Fix violations of uintcast

* go mod tidy

* Add exclusion to nogo for darwin build

* Add test for math.Int

* Move some things to const so they are assured not to exceed int64

* Self review

* lint

* fix tests

* fix test

* Add init check for non 64 bit OS

* Move new deps from WORKSPACE to deps.bzl

* fix bazel build for go analysis runs

* Update BUILD.bazel

Remove TODO

* add math.AddInt method

* Add new test casts

* Add case where builtin functions and declared functions are covered

* Fix new findings

* cleanup

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
Co-authored-by: Nishant Das <nishdas93@gmail.com>
2022-03-11 09:34:30 +00:00
..
comparesame Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
cryptorand Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
errcheck Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
featureconfig Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
ineffassign Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
interfacechecker Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
maligned Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
nop Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
properpermissions Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
recursivelock Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
shadowpredecl Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
slicedirect Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
uintcast Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
README.md Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00

Running analyzer unit tests

Analyzers' unit tests are ignored in bazel's build files, and therefore are not being triggered as part of the CI pipeline. Because of this they should be invoked manually when writing a new analyzer or making changes to an existing one. Otherwise, any issues will go unnoticed during the CI build.

The easiest way to run all unit tests for all analyzers is go test ./tools/analyzers/...