[Upstream #153] npm run setup:all安装时一直报 pillow` (v10.3.0) 的错

[ivanzud]

Upstream Issue Mirror

• Upstream issue: npm run setup:all安装时一直报 pillow` (v10.3.0) 的错 666ghj/MiroFish#153
• Upstream repository: 666ghj/MiroFish
• State: open
• Author: heiheiheibj
• Labels: question
• Last updated: 2026-03-11T18:41:35Z

Summary

Resolved 188 packages in 5.27s Built mirofish-backend @ file:///D:/MiroFish/backend x Failed to build pillow==10.3.0 |-> The build backend returned an error -> Call to backend.build_wheel` failed (exit code: 1) [stderr] Traceback (most recent call last): File "", line 14, in requires = get_requires_for_build({}) File "C:\Users\Administrator\AppData\Local\uv\cache\builds-v0.t…

Local Coverage

• Status: covered
• Summary: The current branch no longer reproduces a pillow build during the default npm run setup:all core install path. setup:backend now maps to a plain uv sync of the core graph/report/OpenAI-compatible backend dependencies, while the heavyweight simulation runtime remains behind the separate setup:backend:simulation entrypoint. A Windows + Python 3.13 dry-run of uv sync --frozen against the current lockfile does not attempt to install pillow at all, and the optional simulation lock now resolves pillow==10.4.0 instead of 10.3.0.
• Local refs: package.json, README.md, README-EN.md, scripts/setup_backend_simulation.py, backend/uv.lock
• Notes: Mirrored into fork issue [Upstream #153] npm run setup:all安装时一直报 pillow` (v10.3.0) 的错 #92 on March 11, 2026. If the reporter still sees pillow==10.3.0 during setup:all, they are likely on an older checkout. The current core path avoids Pillow entirely and the optional simulation path now locks Pillow to 10.4.0.