Skip to content

Python runner: gauge-python 0.4.11 (UDS patch)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@johnboyes johnboyes released this 15 Jan 00:11
v0.4.11-uds
b03eb77
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Why

  • Some sandboxed environments (e.g., CodeRabbit job containers) block loopback TCP inside the container. When Gauge tries to connect to the python runner over 127.0.0.1:, the connection fails with "connection refused". Unix Domain Sockets are permitted, so enabling UDS lets Gauge specs with python step implementations be executed in these environments.

What

  • start.py: Bind the gRPC server on unix:/tmp/gauge-python.sock instead of a TCP port. Clean up any existing socket file before binding to avoid "address already in use" errors. Force port variable to 1 to work around gRPC returning 0 for UDS (the value itself is unused; only the socket path matters). Update startup log to advertise "unix:/tmp/gauge-python.sock" so Gauge core can parse and dial the socket.

Install

  • Download gauge-python-0.4.11.zip and install with: 
    gauge install python --file gauge-python-0.4.11.zip
  • Verify installation: gauge version (should show python plugin 0.4.11)

Compatibility

  • Requires corresponding UDS support in Gauge core (ability to parse "unix:" addresses and dial gRPC over UDS). Use Gauge 1.6.20-uds or later.
  • Not backward compatible with unpatched Gauge core 1.6.20, which expects a numeric port and will timeout connecting to the runner.

Checksums

  • Verify the .sha256 file with: sha256sum -c gauge-python-0.4.11.zip.sha256
Assets 4
Loading