Include standard Go source code check tools in the development workflow.
What it does
It fixed all the errors reported by go vet mainly unreachable code and lock copy errors.
Accomplishments that we're proud of
Catching suspicious structs at build time.
What we learned
Including Go tools in the development workflow can help you catch edge cases.
What's next for Fix Go Vet Lock Copy Value Errors
If the fixes are merged we should update Dockerfile to do a cycle of go test and go vet on each build. Also, the same should be done for all the pipelines.
Since sync.Mutex is pointer value. We need to be careful to initialize with the proper value each time we define a new Log or LBHost