[GH-ISSUE #1418] example_node.py not working after install ComfyUI-Manager #586

New issue

Closed

opened 2026-10-27 21:19:32 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-27 21:19:32 +00:00

Owner

Originally created by @siraphopp on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1418

example_node.py from example_node.py.example which is from the ComfyUI official is not working after install ComfyUI-Manager. But the other custom nodes from GitHub is working fine.

Originally created by @siraphopp on GitHub (Jan 9, 2025). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1418 example_node.py from example_node.py.example which is from the ComfyUI official is not working after install ComfyUI-Manager. But the other custom nodes from GitHub is working fine.

bsakaguchi closed this issue

2026-10-27 21:19:32 +00:00

bsakaguchi commented

2026-10-27 21:19:33 +00:00

Author

Owner

@mferris77 commented on GitHub (Jan 10, 2025):

I've been looking for information related to this as I'm fairly new to Comfy but have been working on a custom script - and it doesn't work anymore. I think it has to do with the recent update to the plugin registry. It seems the node manager is scanning all custom nodes for a 'version' which it expects to find in a node's git package (to determine if a new version is available, perhaps?) - but if it's not a custom node that came from github, there's no version information available and it fails to properly load the node.

Having one of these unknown custom nodes also seems to signficantly slow down the custom node manager whenever it is opened as the manager appears to be fetching something from github (extension node map) and hangs for a good 30-45 seconds. At least I presume the two issues are related.

It would be nice if there was a way to indicate that a certain node/folder should not get verified or validated, such as when we're developing our own nodes or choose not to publish them to github.

@mferris77 commented on GitHub (Jan 10, 2025): I've been looking for information related to this as I'm fairly new to Comfy but have been working on a custom script - and it doesn't work anymore. I think it has to do with the recent update to the plugin registry. It seems the node manager is scanning all custom nodes for a 'version' which it expects to find in a node's git package (to determine if a new version is available, perhaps?) - but if it's not a custom node that came from github, there's no version information available and it fails to properly load the node. Having one of these unknown custom nodes also seems to signficantly slow down the custom node manager whenever it is opened as the manager appears to be fetching something from github (extension node map) and hangs for a good 30-45 seconds. At least I presume the two issues are related. It would be nice if there was a way to indicate that a certain node/folder should not get verified or validated, such as when we're developing our own nodes or choose not to publish them to github.

bsakaguchi commented

2026-10-27 21:19:33 +00:00

Author

Owner

@ltdrdata commented on GitHub (Jan 11, 2025):

Try updating ComfyUI-Manager to the latest version.
As of version V3.6.1, there are no issues.

@ltdrdata commented on GitHub (Jan 11, 2025): Try updating ComfyUI-Manager to the latest version. As of version V3.6.1, there are no issues. ![image](https://github.com/user-attachments/assets/7aeec447-c417-4c18-9377-dba622ad4207)