WASM cache fails to download when venv is under Program Files (Windows)

Open

#126 opened on Sep 17, 2026 0 comments 0 reactions 1 assignee View on GitHub

@ansBAkula is already working on this.

Since Sep 18, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

User Story Description

As a user or system integrator

I want the SAF Visor to successfully download and cache VTK WebAssembly (WASM) assets on first run

So that the application starts correctly for non‑admin users even when the product was installed under C:\Program Files\....

Background

On first run, trame_vtklocal downloads and caches VTK WASM assets into the Python virtual environment. The module writes to a path like:

C:\Program Files\ANSYS Inc\SAF Solutions\...\.venv\Lib\site-packages\trame_vtklocal\module\serve\wasm\9.6.1

When the virtualenv is located under C:\Program Files, Windows prevents non‑elevated processes from creating/writing folders there. This causes pathlib.Path.mkdir() in trame_vtklocal/module/wasm.py to raise a PermissionError / FileNotFoundError on first run, e.g. "Access is denied" or "[WinError 3] The system cannot find the path specified".

Acceptance Criteria

A fresh install of SAF under C:\Program Files followed by a non‑admin run does not raise PermissionError and the WASM assets are downloaded to a writable location.

Additional Links

No response

Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.

Name and Version for Third Parties

No response

Dominant language: Python
Stars: 1
Forks: 0
Avg merge: 1d 21h
Merged PRs (30d): 47

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.