vgi-python 0.8.10__tar.gz → 0.8.11__tar.gz

{vgi_python-0.8.10 → vgi_python-0.8.11}/.github/workflows/release.yml

@@ -56,6 +56,80 @@ jobs:
           name: dist-fixtures
           path: dist-fixtures/
 
+  build-docker-image:
+    name: Build & push vgi-fixtures image (${{ matrix.short }})
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write # push to GHCR
+    # One image per fixture worker, selected via the VGI_FIXTURE_WORKER build arg.
+    # The VGI extension's container transport uses plain `oci://…` string
+    # LOCATIONs (no struct env), so the worker must be baked into the tag rather
+    # than passed at runtime. Tags: ghcr.io/query-farm/vgi-fixtures:<ver>-<short>
+    # (plus :<ver> and :latest for the base worker). max-parallel: 1 so the heavy
+    # pip-install layer is built once and reused from the gha cache by the rest.
+    strategy:
+      fail-fast: false
+      max-parallel: 1
+      matrix:
+        include:
+          - { short: worker, worker: vgi-fixture-worker, latest: true }
+          - { short: versioned, worker: vgi-fixture-versioned-worker }
+          - { short: versioned-tables, worker: vgi-fixture-versioned-tables-worker }
+          - { short: attach-options, worker: vgi-fixture-attach-options-worker }
+          - { short: bad-protocol, worker: vgi-fixture-bad-protocol-worker }
+          - { short: bad-enum, worker: vgi-fixture-bad-enum-worker }
+          - { short: simple-writable, worker: vgi-fixture-simple-writable-worker }
+    steps:
+      - uses: actions/checkout@v7
+
+      # The image installs the exact wheels this release publishes.
+      - name: Download vgi wheel
+        uses: actions/download-artifact@v8
+        with:
+          name: dist-vgi
+          path: dist
+      - name: Download vgi-fixtures wheel
+        uses: actions/download-artifact@v8
+        with:
+          name: dist-fixtures
+          path: dist
+
+      - name: Compute image tags
+        id: meta
+        run: |
+          ver="${{ github.event.release.tag_name }}"
+          ver="${ver#v}" # normalize a leading v (v0.8.2 -> 0.8.2)
+          img="ghcr.io/query-farm/vgi-fixtures"
+          tags="$img:$ver-${{ matrix.short }}"
+          if [ "${{ matrix.latest }}" = "true" ]; then
+            tags="$tags,$img:$ver,$img:latest"
+          fi
+          echo "tags=$tags" >> "$GITHUB_OUTPUT"
+
+      - uses: docker/setup-buildx-action@v3
+
+      - name: Log in to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build & push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: packages/vgi-fixtures/docker/Dockerfile
+          platforms: linux/amd64
+          build-args: |
+            VGI_FIXTURE_WORKER=${{ matrix.worker }}
+          tags: ${{ steps.meta.outputs.tags }}
+          push: true
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+
   publish-vgi:
     name: Publish vgi to PyPI
     needs: build

{vgi_python-0.8.10 → vgi_python-0.8.11}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vgi-python
-Version: 0.8.10
+Version: 0.8.11
 Summary: Vector Gateway Interface - Connect DuckDB to external programs via Apache Arrow
 Project-URL: Homepage, https://query.farm
 Project-URL: Repository, https://github.com/Query-farm/vgi-python

vgi_python-0.8.11/packages/vgi-fixtures/docker/Dockerfile

@@ -0,0 +1,39 @@
+# syntax=docker/dockerfile:1
+#
+# vgi-fixtures — example/test VGI worker images for the VGI DuckDB extension.
+#
+# Each worker speaks vgi-rpc over stdin/stdout; the extension's oci:// container
+# transport runs `docker run -i ... IMAGE stdio` and pipes the worker like a
+# subprocess (full fidelity — same semantics as the local subprocess transport,
+# unlike HTTP). Which worker runs is selected by VGI_FIXTURE_WORKER, baked per
+# image tag via the build arg below (overridable at runtime with `-e`).
+#
+# Built from the SAME wheels published to PyPI in the release (the release
+# workflow copies them into ./dist), so the image matches the released
+# vgi-fixtures exactly — no separate source path to drift.
+
+FROM python:3.13-slim
+
+# vgi-python (core) + vgi-fixtures (worker entry points + the vgi/_test_fixtures
+# sources the fixtures wheel force-includes). Installing both local wheels; the
+# extras the fixtures require ([duckdb], [test-fixtures-writable]) resolve from
+# PyPI. Kept as one heavy layer so the per-worker ARG below doesn't bust it.
+COPY dist/*.whl /tmp/wheels/
+RUN pip install --no-cache-dir /tmp/wheels/*.whl && rm -rf /tmp/wheels
+
+# Worker selection — placed AFTER the install so the (expensive) layer above is
+# shared across every per-worker tag; only this cheap tail rebuilds per worker.
+ARG VGI_FIXTURE_WORKER=vgi-fixture-worker
+ENV VGI_FIXTURE_WORKER=${VGI_FIXTURE_WORKER}
+
+COPY packages/vgi-fixtures/docker/docker-entrypoint.sh /usr/local/bin/vgi-fixtures-entrypoint
+RUN chmod +x /usr/local/bin/vgi-fixtures-entrypoint
+
+LABEL org.opencontainers.image.source="https://github.com/Query-farm/vgi-python" \
+      org.opencontainers.image.description="Example/test VGI worker (stdio) for the VGI DuckDB extension" \
+      org.opencontainers.image.licenses="MIT"
+
+# The extension passes the transport mode as argv[1]; stdio is the default + only
+# mode this image implements.
+ENTRYPOINT ["/usr/local/bin/vgi-fixtures-entrypoint"]
+CMD ["stdio"]

vgi_python-0.8.11/packages/vgi-fixtures/docker/docker-entrypoint.sh

@@ -0,0 +1,46 @@
+#!/bin/sh
+# Entrypoint for the vgi-fixtures container image.
+#
+# The VGI DuckDB extension's container (oci://) transport invokes the image as
+#   docker run -i ... IMAGE <mode>
+# where <mode> is the transport it wants: "stdio" (private per-process, piped over
+# stdin/stdout exactly like the subprocess transport) or "tcp"/"http" (a shared
+# server). This image implements *stdio only* — the fixture workers speak vgi-rpc
+# over stdin/stdout and advertise no farm.query.vgi.transports label, so the
+# extension stays on per-process stdio for it.
+#
+# Which fixture worker runs is chosen by $VGI_FIXTURE_WORKER. It is baked per image
+# tag via the Dockerfile build arg (e.g. the ":<ver>-versioned" tag bakes
+# vgi-fixture-versioned-worker) and can be overridden at runtime with
+#   docker run -e VGI_FIXTURE_WORKER=vgi-fixture-bad-enum-worker ...
+set -eu
+
+mode="${1:-stdio}"
+worker="${VGI_FIXTURE_WORKER:-vgi-fixture-worker}"
+
+# Only ever exec a published vgi-fixture-* console script — never an arbitrary
+# command smuggled in through the env var.
+case "$worker" in
+	vgi-fixture-*) : ;;
+	*)
+		echo "vgi-fixtures: refusing to run non-fixture command '$worker'" >&2
+		exit 64
+		;;
+esac
+
+case "$mode" in
+	stdio)
+		# The worker serves vgi-rpc over stdin/stdout and runs until EOF.
+		exec "$worker"
+		;;
+	tcp | http)
+		echo "vgi-fixtures: transport '$mode' is not supported by this image (stdio only)." >&2
+		echo "             It advertises no farm.query.vgi.transports label, so the extension" >&2
+		echo "             uses per-process stdio; do not force connection=$mode for it." >&2
+		exit 64
+		;;
+	*)
+		echo "vgi-fixtures: unknown transport mode '$mode' (expected: stdio)" >&2
+		exit 64
+		;;
+esac

{vgi_python-0.8.10 → vgi_python-0.8.11}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "vgi-python"
-version = "0.8.10"
+version = "0.8.11"
 description = "Vector Gateway Interface - Connect DuckDB to external programs via Apache Arrow"
 readme = "README.md"
 keywords = [

{vgi_python-0.8.10 → vgi_python-0.8.11}/uv.lock

@@ -2228,7 +2228,7 @@ requires-dist = [
 
 [[package]]
 name = "vgi-python"
-version = "0.8.10"
+version = "0.8.11"
 source = { editable = "." }
 dependencies = [
     { name = "click" },