mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1722] [Bug]: global uv setting exclude-newer causes install failure #524
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#524
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tvanantwerp on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1722
App Version
ComfyUI Desktop 0.9.1 (fresh install, never successfully launched)
Expected Behavior
On first-run setup on macOS arm64, the desktop installer should either (a) be insulated from the user's global uv configuration, or (b) fail with a clear, actionable error message — rather than ending up in an unsatisfiable resolver state because of a user-level uv.toml setting.
Actual Behavior
The desktop's bundled uv binary reads the user's global config at
~/.config/uv/uv.toml. If that file setsexclude-newer, the resolver can't find a satisfiable torch candidate on macOS arm64 and the install never completes.Two suggested fixes for the desktop installer:
--no-config(or setUV_NO_CONFIG=1) on the install invocations so the desktop's Python bootstrap can't be derailed byuser-level uv config. The desktop ships its own bundled uv precisely to control this environment; inheriting arbitrary user
uv.toml defeats that.
Secondary follow-on bug, regardless of root cause: after a failed install leaves a partial
.venv, the next launch runsuv venv --python 3.12 --python-preference only-managedwhich promptsA virtual environment already exists at .venv. Do you want to replace it?— non-interactively answered "no" — and aborts:The installer should pass
--clear(orUV_VENV_CLEAR=1) so a failed first attempt doesn't permanently wedge the install and require the user to manually find and delete the stale.venv.Steps to Reproduce
~/.config/uv/uv.tomlcontaining something like:exclude-newer = "2026-04-28"uv pip install/uv syncfail with "No solution found when resolving dependencies" and the macOS-arm64-wheel hint.uv venvfails because the partial.venvalready exists.Debug Logs
Browser Logs
n/a
Settings JSON
n/a
Other
uvat/Applications/ComfyUI.app/Contents/Resources/uv/macos/uv┆Issue is synchronized with this Notion page by Unito