[wyongzhi]

What was the problem/requirement? (What/Why)

#308 switched hatch.toml to {env:HATCH_UV} pip install .... On the integ CodeBuild runner hatch is installed under C:\Program Files\Python313, so the expansion is an unquoted path with a space and cmd runs C:\Program:

pre-install [1] | C:\Program Files\Python313\Scripts\uv.EXE pip install -r requirements-integ-testing.txt
'C:\Program' is not recognized as an internal or external command

hatch run integ-ci:setup fails before any test runs (3ds Max Integration Tests run #61).

What was the solution? (How)

Quote the expansion: "{env:HATCH_UV}" pip install ... in every pre-install-commands and sync entry (default, integ, integ-ci).

What is the impact of this change?

CI only. No source or behaviour change.

How was this change tested?

Reproduced on a Windows machine with hatch installed under C:\Program Files\...: the unquoted form fails with the exact CodeBuild error; the quoted form creates the default and integ-ci.py3.11-2026 envs, pytest resolves from inside the hatch env, and hatch run test passes (483). Verified with both uv-backed (HATCH_ENV_TYPE_VIRTUAL_UV_PATH set) and virtualenv-backed envs.

Then ran the CodeBuild path end to end on that machine: hatch -e integ-ci.py3.11-2026 run test -m adaptor (3ds Max 2026 + V-Ray 7). Env creation and both pre-install commands succeed; 7 passed, 1 xfailed, 3 failed for reasons unrelated to this change (headless session has no GPU for the V-Ray GPU lightmix case; vrmesh_path_remap fails identically on mainline on this machine; batch_render expected images are updated in a separate PR).

On macOS, a uv copy placed in a directory with a space reproduces the same class of failure (/bin/sh: /tmp/dir: No such file) and the quoted form passes; hatch run lint clean.

Was this change documented?

No, CI-internal.

Did you modify schema files?

• Yes
• No

Is this a breaking change?

No.

[github-actions]

Claude review · advisory

Reviewed 89a8391 (full review): 0 findings.

Open: 0 blocking · 0 should-fix · 0 nit. ✅ Nothing blocking.

_{Fix or reply to each thread; the next revision's review re-checks open threads and resolves those it agrees are handled. Resolving a thread yourself also closes it. Later revisions review only what changed.}