Remove redundant VIRTUAL_ENV variable from Dockerfile

[adamtheturtle]

Replace the redundant VIRTUAL_ENV environment variable with UV_PROJECT_ENVIRONMENT, which holds the same value and is already set. This reduces duplicate environment variable definitions in the Dockerfile.

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk: Docker build env var cleanup and a test-only assertion change to ignore Jetty version differences; no production runtime logic changes.

Overview
Removes the redundant VIRTUAL_ENV variable from the mock VWS Flask server Dockerfile, using UV_PROJECT_ENVIRONMENT for both venv creation and PATH setup.

Updates tests/mock_vws/test_query.py to make the Jetty HTML error-body assertion tolerant of Jetty version changes by regex-normalizing the Powered by Jetty:// <version> footer before comparing expected vs actual.

^{Written by Cursor Bugbot for commit 94ff092. This will update automatically on new commits. Configure here.}

[cursor]

Removing standard VIRTUAL_ENV breaks Python venv detection

Medium Severity

VIRTUAL_ENV is a Python ecosystem standard env var used by tools like pip, shell prompts, and other utilities to detect an active virtual environment. UV_PROJECT_ENVIRONMENT is uv-specific and not a substitute — they serve different purposes. Removing VIRTUAL_ENV means standard Python tooling inside the container won't recognize the venv. The comment on lines 12–13 referencing the pythonspeed article also becomes misleading, since that technique explicitly relies on setting VIRTUAL_ENV.

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}