1 Commits
Author SHA1 Message Date
zooqueen 55d12d9e97 generate the service half, and reach a sibling container at the host
Two failures, neither in this code.

  internal/test/my_service could not build: `undefined: MyServiceServer`. Its
    .psrpc.go half is gitignored on purpose (internal/test/.gitignore carries
    **/*.psrpc.go) — generated, not committed — so a fresh checkout has the
    .pb.go and none of the service code that goes with it, and nothing in the
    gate ever generated it. It does now, from the plugin in this repo. Only the
    psrpc half: the .pb.go beside it IS committed, and regenerating that too
    rewrites it against whatever protoc the runner carries.

    From the package directory, as gen.go does. paths=source_relative places
    output beside the .proto AS NAMED, so running it from the root writes
    my_service.psrpc.go into the root and every build then reports `found
    packages psrpc and my_service in <root>`.

  internal/bus dialled 127.0.0.1 for containers it had just started:

      bustest.go:51: dial tcp 127.0.0.1:32769: connect: connection refused

    CI runs the job inside a container with the host's /var/run/docker.sock
    bound in, so nats and redis come up as SIBLINGS — published on the HOST's
    loopback, while the job's own 127.0.0.1 is a different interface with
    nothing on it. dockertest reports the daemon's view; the port it chose is
    right and the host is not, so hostPort keeps the port and answers the host:
    the bridge gateway from inside a container, loopback outside one, and
    DOCKER_TEST_HOST ahead of both.

Verified against a real daemon: internal/bus goes from refused to ok in 18s,
and the gate's own command — generate, build, then the package list it already
uses — passes 19 packages, exit 0.
2026-08-11 00:12:35 -07:00