Million hours waiting for the manager to install missing nodes

[moreAImore]

Expected Behavior

I did not use comfy for a long time, I came back to see the new menus for installing mising nodes and this is working really bad, it should install very quickly but instead:

Actual Behavior

It is blocked for dozens of minutes now here:

Steps to Reproduce

update your comfy install (normal update bat file)
download this workflow : https://civitai.com/models/1484173?modelVersionId=1678841
open it, download the models missed, and while they are downloading press next to find the missind nodes menu and install them

Debug Logs

FETCH DATA from: E:\c\ComfyUI\custom_nodes\ComfyUI-Manager\extension-node-map.json [DONE]

[moreAImore]

Wait its even worse, I closed the windows and now it said that neither was installed (despite what the screenshot showing that one of them is installed)

[christian-byrne]

Can you share the full output of the terminal?

[Fitzeputz]

I have the same problem, and for me the installation attempt doesn't appear in the terminal

Strangely enough I don't even find the option to open the Node Manager the regular way. There's only the button when that pops up when you import a workflow for which you are missing nodes.

Disabling the new menu didn't yield anything either.

[christian-byrne]

Do you have ComfyUI-Manager custom node installed in custom_nodes folder?

[Fitzeputz]

Okay, now that's strange. You're right, it was missing for some reason. After installing the manager again it works properly for me.

I assume then that a user being able to access the Node Management UI without having the manager is the actual bug.

[ltdrdata]

Currently, the development to add ComfyUI-Manager as a default dependency is being done in a separate branch, but it may have been unintentionally reflected on the frontend.

[christian-byrne]

Hm, it seems that this PR is the problem: Comfy-Org/ComfyUI_frontend#3395

It was included in 1.16 when it should have been released alongside the Manager migration PR.

For now, it means the user can open the new Manager UI from the Missing Nodes dialog. It will be opened directly on the "Missing" tab. Downloading will work unless they don't have the Manager installed as a custom node, as was reported here.

I'm not sure if I should change this or not. It does not break any core functionality of the app and it should not cause any bugs for most users. It will also allow for early testing of the new UI across a smaller subset of users.

Ultimately, the user can simply use the old manager if they encounter bugs. As we have not removed the buttons from the topbar menu.

[moreAImore]

Update: opening the manager from the uppoer button, and landing on the classic page related to the manager still works very will, missing nodes button worked good. PLEASE DO NOT REMOVE THE OLD MANAGER MENU, At least keep it optional. It's really good

[christian-byrne]

It will be kept optional, don't worry.

[SuperFurias]

i think i understand what's the problem. the new desktop install of ComfyUI automatically installs ComfyUI-Manager somewhere else and this messes up things a bit

there are two different places for the custom nodes.

the first one is:

AppData\Local\Programs@comfyorgcomfyui-electron\resources\ComfyUI\custom_nodes

and inside here, there is ONLY the custom node ComfyUI-Manager

the second one is:
when you install the desktop app, the app asks you to choose another folder to do stuff, i don't remember exactly what stuff, but asks you to choose a folder. and that folder has another custom_nodes folder.
that's the folder where comfui manager installs custom nodes. and its empty by default

i think that's the problem why the new ui for missing nodes doesn't work. because there is nothing installed in the custom_nodes folder

[christian-byrne]

@SuperFurias Thanks for looking into the issue in depth. We shall investigate based on your findings.

For anyone arriving: If you are using the new Manager UI, keep in mind it is in a Beta stage. If you have issues, try this:

• Ensure the ComfyUI-Manager custom node is installed and updated
• If it is installed and there's still issues with the new UI, you can simply go back to the old Manager UI for now (using the "Manager" button in the top menu bar)
• If you did find issues, please report them here and we will fix it. It is appreciated.

[aokocax]

Okay, now that's strange. You're right, it was missing for some reason. After installing the manager again it works properly for me.

I assume then that a user being able to access the Node Management UI without having the manager is the actual bug.

Delete and reinstall the manager fixed the same problem for me.

[ltdrdata]

Until the new UI is fully established, the existing method will still be available using --enable-manager-legacy-ui.

[marduk191]

i thought the point of stable versioning was to avoid this nonsense? so basically there are zero stable versions without rolling back to known good stable releases because stable releases are not stable and rolling releases are unstable by nature.