Comfy-Org / Comfy-Org/ComfyUI-Manager

Registry node extraction pending: mediahub-cloud shows No nodes found

Open
#3,044 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
16.1k
Forks
2.5k
Avg merge
5d 4h
Merged PRs (30d)
13

Description

## Summary

`mediahub-cloud` is visible and installable in ComfyUI Manager / Desktop, but the Node Pack Info panel shows `No nodes found`.

This appears to be caused by the Registry version extraction status being stuck at `pending`, even though the version itself is active.

Backend tracking issue: https://github.com/Comfy-Org/registry-backend/issues/185

## Node

- Registry page: https://registry.comfy.org/nodes/mediahub-cloud
- Repository: https://github.com/vantang/ComfyUI-MediaHub
- Version: `0.1.0`
- Version id: `4307177c-bac2-4a96-8558-a69a73ea373f`

## Current Registry API state

```bash
curl -s "https://api.comfy.org/versions?nodeId=mediahub-cloud&include_status_reason=true&pageSize=1" \
| python3 -c "import json,sys; v=json.load(sys.stdin)["versions"][0]; print(v["status"], v.get("comfy_node_extract_status"))"
```

Output on 2026-07-03:

```text
NodeVersionStatusActive pending
```

## Manager / Desktop symptom

In the Node Pack Info panel, the pack is listed as active/installable, but the `NODES` section says:

```text
No nodes found
The pack's nodes either could not be parsed, or the pack is a frontend extension only and doesn't have any nodes.
```

## Expected behavior

Once the Registry node extraction job completes, Manager should show the nodes exported by `NODE_CLASS_MAPPINGS`.

## Notes

The package has a standard ComfyUI custom-node entry point and the nodes load in ComfyUI:

```python
# __init__.py
from .nodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
WEB_DIRECTORY = "./js"
```

This issue is filed here because Manager/Desktop users see the symptom in this UI. The backend/root tracking issue is Comfy-Org/registry-backend#185.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked registry-backend issue and reproduce the API query for version 0.1.0 to inspect its extraction status. Review the package entry point in __init__.py and the exported NODE_CLASS_MAPPINGS, then verify that the Manager Node Pack Info panel lists the extracted nodes once the registry job completes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.