4 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
claude-bot	3c77d34b7e	docs(runner): name the protoc coupling and fix a mechanism claim ... Both from the cross-review, both fair. "Go setzt CGO_ENABLED=0" is right about the effect and wrong about the mechanism: Go does not set the variable, cgo simply stays off when no C compiler is found, and go env then reports 0. Reworded. And protoc on an instance-wide runner ties every repository to the distribution's version -- 3.21.x on Debian 12. Unlike make and gcc that is a code generator, so a distro upgrade changes generated code for all users at once. The comment says so now, and says where a project that needs its own version should pin it instead of raising it here for everybody.	2026-08-18 23:01:34 +02:00
claude-bot	8c83fb372b	feat(runner): install the build toolchain compiled languages need ... The runner is host-mode, so there is no image bringing tools along: what is not on this LXC, no job has. Measured on l.kirchner/patchmgr, a Go project, where all six CI jobs were assigned and every one of them died in the first seconds: make all make: command not found go test -race go: -race requires cgo; enable cgo by setting CGO_ENABLED=1 make proto sudo: command not found Four packages, each for a reason: make the gate commands are make targets gcc Go turns CGO_ENABLED off when it finds no C compiler, and the race detector cannot be built without cgo protobuf-compiler protoc itself libprotobuf-dev the well-known .proto includes under /usr/include/google/protobuf; without them protoc fails even though the binary is there sudo stays absent on purpose. A workflow must not be able to install anything on this runner -- what is needed is declared here, in the script, and not in somebody's pipeline. That also keeps the security note at the top of this file honest: the LXC owns nothing, and it gains nothing at a workflow's request. Go is not in the list. Projects fetch it through actions/setup-go, because CI matrices run more than one version. Applied to the running LXC (301 on pve-gamer) while the runner was idle, then verified: make 4.3, gcc 12.2.0, libprotoc 3.21.12, 11 .proto includes present. The service PATH already contains /usr/bin, so no restart was needed.	2026-08-18 22:54:54 +02:00
claude-bot	6543fd77d8	fix(nexus-db): address codex review — early encoding guard, robust helpers ... - assert encoding BEFORE role/password mutation on re-run, so an old SQL_ASCII DB aborts with no side effects (codex finding 1) - ensure_utf8_locale_active honours its locale argument consistently in match, locale.gen line and export (codex finding 2) - assert_db_encoding_utf8 uses argv-clean runuser psql with :'db' literal binding instead of nested su -c shell; docs keep su - postgres -c (codex finding 3)	2026-06-13 14:34:35 +02:00
claude-bot	bd4293f53e	fix(nexus-db): enforce UTF8 encoding at install time (issue #8) ... A PostgreSQL cluster/database freezes its encoding at initdb / CREATE DATABASE time; a C (non-UTF-8) locale yields a SQL_ASCII cluster, which makes psycopg3 return bytes and crashes SQLAlchemy. Harden the installer and add a reusable pattern for future DB installers: - ensure_utf8_locale_active: generate AND activate en_US.UTF-8 for the install process before the server package runs initdb; abort if the locale is not actually available - create the database explicitly with TEMPLATE template0 ENCODING 'UTF8' LC_COLLATE/LC_CTYPE 'en_US.UTF-8' instead of inheriting the cluster default - assert_db_encoding_utf8: post-install guard, abort with an actionable message if pg_encoding_to_char is not UTF8 (catches old SQL_ASCII DBs on re-run too) - credentials/README docs use su - postgres -c (minimal LXCs have no sudo)	2026-06-13 14:30:40 +02:00