indygreg / indygreg/PyOxidizer

Packaging torch fails with File exists (Windows)

Open
#403 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

**Setup**
```ps
PS C:\vinegar2> pyoxidizer --version
PyOxidizer 0.16.0
commit: 4053178f2ba11d29f497d171289cb847cd07ed77
source: https://github.com/indygreg/PyOxidizer.git
pyembed crate location: version = "0.16.0"

PS C:\vinegar2> [System.Environment]::OSVersion.Version

Major Minor Build Revision
----- ----- ----- --------
10 0 21382 0
```
Minimal `pyoxidizer.bzl` (pip installs `torch`):
[pyoxidizer.bzl.txt](https://github.com/indygreg/PyOxidizer/files/6517970/pyoxidizer.bzl.txt)

**Error**
```
PS C:\vinegar2> pyoxidizer run

adding extra file lib/zoneinfo/_zoneinfo.py to .
adding extra file python3.dll to .
adding extra file python39.dll to .
adding extra file vcruntime140.dll to .
adding extra file vcruntime140_1.dll to .
installing files to C:\vinegar2\.\build\x86_64-pc-windows-msvc\debug\install
error: error calling build(): Runtime(RuntimeError { code: "TUGGER_FILE_MANIFEST", message: "Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist. (os error 183)", label: "FileManifest.build()" })
```
The error translates to `File couldn't be created since it already exists`.

**Expected**
An interactive shell where `import torch` works.

Contributor guide

No contributing guide indexed for this repository

First steps

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

Research direction

Start with the attached minimal pyoxidizer.bzl configuration and reproduce the failure with `pyoxidizer run` on Windows. Trace the `FileManifest.build()` error and the reported existing-file conflict; done means the installation completes and the resulting interactive shell can successfully `import torch`.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.