mirror of
https://github.com/Comfy-Org/ComfyUI-Manager.git
synced 2026-11-04 23:37:31 +00:00
[GH-ISSUE #1659] Bug: Custom node dependencies failing to install through comfy-cli #715
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/ComfyUI-Manager#715
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 @oprogramadorreal on GitHub (Mar 14, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1659
Description
After commit 0a60a44, the functionality to install custom node dependencies from workflow files via comfy-cli has stopped working. This affects users of comfy-cli who use the
node install-deps --workflowcommand.Reproduction Steps
pip install comfy-clicomfy node install-deps --workflow="img2txt_ollama_vision.json"Expected: Custom nodes (
comfyui-easy-useandcomfyui-ollama) should be installedActual: No custom nodes are installed despite logs showing installation attempts
Terminal output upon failure
Additional Context
This issue impacts automation workflows that depend on comfy-cli for installing dependencies programmatically. I've also reported this issue in the comfy-cli repository, but since the root cause appears to be in ComfyUI-Manager, addressing it here would be more effective.
I've verified that rolling back to the commit immediately before 0a60a44 resolves this issue.
Additional Information
Operating System: Windows 11
Python Version: 3.11.9
comfy-cli Version: 1.3.8
@drmbt commented on GitHub (Mar 14, 2025):
having the same issue, i've checked out this latest hash but it seems to be missing a channel requirement now
@oprogramadorreal commented on GitHub (Mar 14, 2025):
@ltdrdata Just did a quick test with your latest commit 39eaa76, and it appears to have resolved the issue. I'll perform additional tests later to confirm. Thanks for the quick response!
@ltdrdata commented on GitHub (Mar 15, 2025):
This issue is fixed.