mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1234] [Bug]: Unable to automatically install db dependency on update #347
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#347
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 @huchenlei on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1234
App Version
Expected Behavior
DB requirement is automatically installed on update.
Actual Behavior
DB error shown on startup
Steps to Reproduce
Receive the update, get stuck in start screen.
Debug Logs
Browser Logs
N/A
Settings JSON
N/A
Other
No response
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (Jul 28, 2025):
It looks like 'db' is not an official dependency in ComfyUI Desktop—it's not present in the standard requirements or handled by the update/install logic. If you're seeing a missing 'db' error, it's likely coming from a custom node, a manual edit, or a mis-generated requirements.txt, not from the core app or its update process (source).
Check your requirements.txt files (both the main one and any under custom_nodes) for any mention of 'db'. If you find it, try removing or correcting that entry, then restart the app to trigger a clean dependency install. If you have custom nodes, one of them might be introducing the 'db' requirement—try disabling them one by one to isolate the source.
If you want to troubleshoot further, you can manually activate the virtual environment and attempt to install dependencies with:
If the problem persists, deleting the
.venvdirectory and restarting the app will force a full reinstall of dependencies (source).Let me know if you spot 'db' in your requirements or if you need help narrowing down which custom node is causing the issue!
To reply, just mention @dosu.
Docs are dead. Just use Dosu.