mirror of https://github.com/OffchainLabs/prysm.git synced 2026-01-07 22:54:17 -05:00

Files

Nishant Das 5d6a406829 Update to Go 1.23 (#14818 )

* Update to Go 1.23

* Update bazel version

* Update rules_go

* Use toolchains_protoc

* Update go_honnef_go_tools

* Update golang.org/x/tools

* Fix violations of SA3000

* Update errcheck by re-exporting the upstream repo

* Remove problematic ginkgo and gomega test helpers. Rewrote tests without these test libraries.

* Update go to 1.23.5

* gofmt with go1.23.5

* Revert Patch

* Unclog

* Update for go 1.23 support

* Fix Lint Issues

* Gazelle

* Fix Build

* Fix Lint

* no lint

* Fix lint

* Fix lint

* Disable intrange

* Preston's review

---------

Co-authored-by: Preston Van Loon <preston@pvl.dev>

2025-01-24 04:53:23 +00:00

comparesame

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

cryptorand

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

errcheck

Update to Go 1.23 (#14818 )

2025-01-24 04:53:23 +00:00

featureconfig

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

gocognit

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

ineffassign

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

interfacechecker

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

logruswitherror

refactor: enable errorlint and refactor code (#14110 )

2024-07-04 22:40:13 +00:00

maligned

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

nop

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

properpermissions

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

recursivelock

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

shadowpredecl

refactor: using slices.Contains to simplify the code (#14781 )

2025-01-09 00:04:45 +00:00

slicedirect

Update to V5 (#13622 )

2024-02-15 05:46:47 +00:00

uintcast

Update to V5 (#13622 )

2024-02-15 05:46:47 +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/...