Skip to content

Remove claude setting#44

Open
ninjadq wants to merge 10 commits into
mainfrom
remove_claude_setting
Open

Remove claude setting#44
ninjadq wants to merge 10 commits into
mainfrom
remove_claude_setting

Conversation

@ninjadq
Copy link
Copy Markdown
Member

@ninjadq ninjadq commented May 12, 2026

No description provided.

ninjadq and others added 10 commits May 8, 2026 06:01
Brainstormed design for upgrading the Operation Cache Controller from
Go 1.24 to Go 1.26 with idiomatic modernization across the codebase.

Approach: 7 sequential stacked PRs (toolchain bump → mockgen regen →
direct dep upgrades → golangci-lint + new linters with suppressions →
mechanical refactor → idiomatic library swaps → Go 1.26-specific
features). Scope explicitly excludes structural and behavioral changes.

Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
golangci-lint v1.64.8 was built with Go 1.24 and refuses to parse
source targeting Go 1.26. v1.64.8 is the last v1.x release, so v2 is
the only forward path. .golangci.yml migrated to v2 schema; lint
surface kept equivalent to the prior config.
The Microsoft Go 1.26 base image defaults GOEXPERIMENT=systemcrypto,
which routes crypto/* through OpenSSL via cgo and requires CGO_ENABLED=1.
ms_nocgo_opensslcrypto keeps the OpenSSL backend (FIPS-friendly) but
resolves libssl via dlopen at runtime, so CGO_ENABLED=0 still produces
a static binary suitable for the distroless final stage.

Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
The previous attempt (ms_nocgo_opensslcrypto) avoided CGO at link time but
still dlopens libssl at runtime, which requires glibc's dynamic linker in
the final image. The distroless/minimal:3.0 base ships neither, so the
manager container failed to start with:

    exec /manager: no such file or directory

Disable systemcrypto entirely so Go's pure-Go crypto is used; the resulting
binary is fully static and runs on the minimal distroless image as before.

Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
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