Skip to content

Fix fork go-tests lint and TLS API failure#266

Open
manu-ns wants to merge 2 commits into
1.22.3-criteofrom
fix/fork-ci-lint-api-tls
Open

Fix fork go-tests lint and TLS API failure#266
manu-ns wants to merge 2 commits into
1.22.3-criteofrom
fix/fork-ci-lint-api-tls

Conversation

@manu-ns

@manu-ns manu-ns commented Jul 6, 2026

Copy link
Copy Markdown

Summary

Details

Validation

  • env GOLANGCI_LINT_CACHE=/tmp/golangci-lint-cache GOPATH=/tmp/consul-gopath GOCACHE=/tmp/consul-go-cache GOMODCACHE=/tmp/consul-gopath/pkg/mod golangci-lint run ./agent/consul ./agent/structs
  • env PATH=/home/manu/git/consul-criteo/bin:$PATH GOPATH=/tmp/consul-gopath GOCACHE=/tmp/consul-go-cache GOMODCACHE=/tmp/consul-gopath/pkg/mod go test . -run '^TestAPI_ClientTLSOptions$' -count=10

manu-ns added 2 commits July 6, 2026 09:33
The public fork go-tests workflow started running again in #265 and exposed these lint failures:

https://github.com/criteo-forks/consul/actions/runs/28659505209

The affected lint debt came from the public fork patch stack, notably:

- #263

- #264

This keeps the change mechanical: gofmt alignment, promoted embedded-field selectors, and bool comparison simplifications only.
After fork go-tests started running again via the public fork workflow fix, this test exposed a latent upstream failure mode:

#265

The same assertion failure reproduces on the upstream v1.22.3 tag, so this is not tied to a Criteo feature PR:

https://github.com/hashicorp/consul/tree/v1.22.3

Accept OS-level server-close errors from the missing-client-certificate handshake in addition to the existing Go TLS alert strings.
@manu-ns
manu-ns requested a review from a team July 6, 2026 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant