xuang7 opened a new pull request, #6130:
URL: https://github.com/apache/texera/pull/6130
### What changes were proposed in this PR?
The single-node NGINX gateway (`bin/single-node/nginx.conf`) has no
`location` block for `/pve/`, so Python Virtual Environment (PVE) REST calls
fall through to the catch-all `location /` → `dashboard-service`, which does
not serve them and returns **404**. In the UI this surfaces as a *"Could not
load Python virtual environments"* popup on every Python UDF operator selection.
The PVE endpoints are served by the amber webserver (`PveResource`,
`@Path("/pve")`, Jersey mounted under `/api/*`) on
`workflow-runtime-coordinator-service:8085`. Both the Angular dev proxy
(`frontend/proxy.config.json`) and the Kubernetes gateway
(`bin/k8s/templates/base/gateway/gateway-routes.yaml`) already route `/pve` →
`/api/pve` to that service; the single-node NGINX config was the only gateway
missing it.
This adds the matching `/pve/` block, rewriting `/pve/*` → `/api/pve/*`
before proxying to the coordinator — mirroring the dev proxy and k8s gateway.
### Any related issues, documentation, discussions?
Related to #5963 (PVE single-node configuration).
### How was this PR tested?
_Pending — manual verification on the single-node Docker stack before this
is marked ready for review._
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
