mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-26 05:17:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
d5bf8376c2
prysm-pulse/tools/analyzers
History
Raul Jordan d4c954648c
Prevent Usage of Stdlib File/Dir Writing With Static Analysis (#7685) 
* write file and mkdirall analyzers

* include analyzer in build bazel

* comments to the single entrypoint and fix validator references

* enforce 600 for files, 700 for dirs

* pass validator tests

* add to nogo

* remove references

* beaconfuzz

* docker img

* fix up kv issue

* mkdir if not exists

* radek comments

* final comments

* Try to fix file problem

Co-authored-by: Ivan Martinez <ivanthegreatdev@gmail.com>
2020-11-09 14:27:03 -06:00
..
comparesame Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
cryptorand Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
errcheck Apply testutils assertions: final cleanup (#7003) 2020-08-25 15:23:06 +00:00
featureconfig Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
ineffassign Fix deepsource findings (#7457) 2020-10-08 08:36:47 +00:00
maligned Various code inspection resolutions (#7438) 2020-10-12 08:11:05 +00:00
nop Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
properpermissions Prevent Usage of Stdlib File/Dir Writing With Static Analysis (#7685) 2020-11-09 14:27:03 -06:00
shadowpredecl Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
slicedirect Unnecessary Slice-to-Slice Conversion analyzer (#7321) 2020-09-23 16:14:34 +00:00
README.md Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00

README.md

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/...