[GH-ISSUE #3256] Incorrect node map for ComfyUI-H3-Continuum: 43 nodes listed, includes VAEDecodeAudio and test fixtures #1130

New issue

Open

opened 2026-10-27 21:26:02 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-27 21:26:02 +00:00

Owner

Originally created by @ukr8b3g-cmyk on GitHub (Sep 9, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3256

Summary

The extension-node-map.json entry for:

https://github.com/ukr8b3g-cmyk/ComfyUI-H3-Continuum

is stale/incorrect. ComfyUI-Manager currently reports 43 nodes and 1 conflict, with VAEDecodeAudio shown as conflicting with ComfyUI Core.

The current H3 Continuum V3.8 public surface exports only 7 nodes. VAEDecodeAudio is a ComfyUI Core node used by the workflow and is not exported by H3 Continuum.

Current incorrect mapping

The Manager DB currently includes many historical/internal/test-only IDs, including examples such as:

H3ContinuumAdvanced
H3ContinuumSamplerV2 ... H3ContinuumSamplerV37
H3CoreContinuumGpuDiagnostic
P24ClearCacheOutput
P24DecodedFixture
P25StoredLongTerminalFixture
P25SyntheticDecodedStressFixture
VAEDecodeAudio

This causes the Manager UI to show 43 nodes and 1 conflict (VAEDecodeAudio).

Expected mapping

Please replace the H3 Continuum node list with the current V3.8 public surface only:

[
  "H3ContinuumSamplerV38",
  "H3ContinuumReferenceAudios",
  "H3ContinuumAssembleSeamV35",
  "H3EasyLoadImage",
  "H3EasyLoadAudio",
  "H3ContinuumLoadVideo",
  "H3ContinuumSecondPassV35"
]

These are the IDs retained by the repository's final _PUBLIC_NODE_DISPLAY_NAMES filtering in nodes.py.

Reproduction

Use current ComfyUI-Manager main (f82970b7cb63ad44928308f980a1d38fda103cbb).
Open Manager and inspect H3 Continuum.
It reports 43 nodes / 1 conflict.
Expanding the card shows historical/internal/test IDs plus VAEDecodeAudio.
Removing the cached extension-node-map does not fix it because the stale mapping is fetched/recreated from the Manager DB/channel.

Notes

H3 Continuum itself should not be changed for this issue; its current public mapping is already limited to the 7 IDs above.
The stale mapping appears in the Manager extension-node-map.json / node_db/new/extension-node-map.json data for this repository.
Removing VAEDecodeAudio from the H3 Continuum mapping also removes the false conflict with ComfyUI Core.

Originally created by @ukr8b3g-cmyk on GitHub (Sep 9, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3256 ## Summary The `extension-node-map.json` entry for: `https://github.com/ukr8b3g-cmyk/ComfyUI-H3-Continuum` is stale/incorrect. ComfyUI-Manager currently reports **43 nodes** and **1 conflict**, with `VAEDecodeAudio` shown as conflicting with ComfyUI Core. The current H3 Continuum V3.8 public surface exports only **7 nodes**. `VAEDecodeAudio` is a ComfyUI Core node used by the workflow and is not exported by H3 Continuum. ## Current incorrect mapping The Manager DB currently includes many historical/internal/test-only IDs, including examples such as: - `H3ContinuumAdvanced` - `H3ContinuumSamplerV2` ... `H3ContinuumSamplerV37` - `H3CoreContinuumGpuDiagnostic` - `P24ClearCacheOutput` - `P24DecodedFixture` - `P25StoredLongTerminalFixture` - `P25SyntheticDecodedStressFixture` - `VAEDecodeAudio` This causes the Manager UI to show `43 nodes` and `1 conflict` (`VAEDecodeAudio`). ## Expected mapping Please replace the H3 Continuum node list with the current V3.8 public surface only: ```json [ "H3ContinuumSamplerV38", "H3ContinuumReferenceAudios", "H3ContinuumAssembleSeamV35", "H3EasyLoadImage", "H3EasyLoadAudio", "H3ContinuumLoadVideo", "H3ContinuumSecondPassV35" ] ``` These are the IDs retained by the repository's final `_PUBLIC_NODE_DISPLAY_NAMES` filtering in `nodes.py`. ## Reproduction 1. Use current ComfyUI-Manager `main` (`f82970b7cb63ad44928308f980a1d38fda103cbb`). 2. Open Manager and inspect **H3 Continuum**. 3. It reports `43 nodes` / `1 conflict`. 4. Expanding the card shows historical/internal/test IDs plus `VAEDecodeAudio`. 5. Removing the cached `extension-node-map` does not fix it because the stale mapping is fetched/recreated from the Manager DB/channel. ## Notes - H3 Continuum itself should not be changed for this issue; its current public mapping is already limited to the 7 IDs above. - The stale mapping appears in the Manager `extension-node-map.json` / `node_db/new/extension-node-map.json` data for this repository. - Removing `VAEDecodeAudio` from the H3 Continuum mapping also removes the false conflict with ComfyUI Core.

bsakaguchi commented

2026-10-27 21:26:03 +00:00

Author

Owner

@ukr8b3g-cmyk commented on GitHub (Sep 9, 2026):

Follow-up: I withdrew the proposed PR and am leaving this as a Manager-side data issue only.

Please update the official H3 Continuum mapping in extension-node-map.json and node_db/new/extension-node-map.json from the stale 43-node list to the current 7-node V3.8 public surface listed in the issue body. In particular, VAEDecodeAudio and the P24/P25 test fixture IDs should not be attributed to H3 Continuum.

No change is required in the H3 Continuum repository itself.

@ukr8b3g-cmyk commented on GitHub (Sep 9, 2026): Follow-up: I withdrew the proposed PR and am leaving this as a Manager-side data issue only. Please update the official H3 Continuum mapping in `extension-node-map.json` and `node_db/new/extension-node-map.json` from the stale 43-node list to the current 7-node V3.8 public surface listed in the issue body. In particular, `VAEDecodeAudio` and the P24/P25 test fixture IDs should not be attributed to H3 Continuum. No change is required in the H3 Continuum repository itself.