-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to load components #1392
Comments
This is fixed, already. |
What is your Manager version number? |
When installed as git, it is automatically installed as nightly version. So, I reinstalled the ComplyUI, and I also installed the manager with version 3.3.6.
And, it was updated to 3.3.7 normally upon restart. Even when I update it later, I'm worried that there's an error like that. And, I think it should always be installed with the latest version, not the nightly version at the first installation. |
This is patched. Update to 3.3.9 and try again. |
The same error occurs in 3.3.9.
There seem to be nodes that cannot be updated.
|
It seems that your ComfyUI installation/status is invalid. And execute
What is displayed? |
This is patched. Update and try again. |
No errors are displayed when updating pythongosssss/ComfyUI-Custom-Scripts#413 After the update, the CompyUI is reinstalled, and it only works fine if it is not updated, and when it is updated, some features do not work the same. Upon update
The cache log is being displayed.
Access denied, update fails. |
Can you check the files of the following directory? "W:\SynologyDrive\Comfy\ComfyUI\custom_nodes\cg-image-picker" Is the directory exists? |
Can you check the files of the following directory? "W:\SynologyDrive\Comfy\ComfyUI\custom_nodes\cg-image-picker" Is the directory there? |
As explained earlier, there is an error like that, but if you click the update again, it will not be updated or updated. The custom node is also installed normally. pythongosssss/ComfyUI-Custom-Scripts#413 Once these two issues occur, they are not resolved. |
That's how it appears when you start the browser without any messages.
The text was updated successfully, but these errors were encountered: