Summary
tests/e2e/npx/npx-smoke-python.test.ts › ships the agent skill and the pi manifest in the tarball (#714) fails on a Windows checkout whose shell puts GNU tar first on PATH (Git Bash: /usr/bin/tar, GNU tar 1.35). The test shells out to tar -tzf "C:\...\package-cache\<hash>.tgz", and GNU tar reads the C: drive prefix as a remote host:
tar (child): Cannot connect to C: resolve failed
Reproduced on main (651237a) and on both #750 and #751; it is the one failure in an otherwise green full vitest run (5634 / 5640 passed). CI (ubuntu) is unaffected.
What would help
Either pass --force-local (GNU tar's switch to stop treating host:path as remote), use a forward-slash / relative path, or list the tarball with a Node tar reader instead of shelling out. Any of the three makes the #714 assertion run on Windows.
Env: Windows 11 Pro, Node 22, Git Bash, GNU tar 1.35.
Summary
tests/e2e/npx/npx-smoke-python.test.ts › ships the agent skill and the pi manifest in the tarball (#714)fails on a Windows checkout whose shell puts GNU tar first on PATH (Git Bash:/usr/bin/tar, GNU tar 1.35). The test shells out totar -tzf "C:\...\package-cache\<hash>.tgz", and GNU tar reads theC:drive prefix as a remote host:Reproduced on
main(651237a) and on both #750 and #751; it is the one failure in an otherwise green fullvitest run(5634 / 5640 passed). CI (ubuntu) is unaffected.What would help
Either pass
--force-local(GNU tar's switch to stop treatinghost:pathas remote), use a forward-slash / relative path, or list the tarball with a Node tar reader instead of shelling out. Any of the three makes the #714 assertion run on Windows.Env: Windows 11 Pro, Node 22, Git Bash, GNU tar 1.35.