When an extension asks through cm.try-install-custom-node for a node
pack that is disabled, the user is asked whether to enable it and
restart. On confirmation the handler posted to
/customnode/toggle_active, which the server does not have, did not
look at the answer, and restarted: ComfyUI came back with the pack
still disabled.
- Enable the pack as the Custom Nodes Manager does: find its row in
/customnode/getlist, put it in the queue, start the queue, and wait
for the queue to report the pack
- Restart only when the queue reports success; otherwise show why the
pack was not enabled
- Leave a queue that is already running alone
- End the wait when the started queue reports without the pack, or
does not report within a minute; a listener left waiting would take
a later report for the same row and restart ComfyUI unasked
- Show the reason when a request made while enabling gets no answer
- Show "Rebooting..." when the restart request gets no answer, which
is what happens when ComfyUI restarts
- Remove the branch for a pack that is not installed: the server does
not send this request for one, and the route it posted to does not
exist
- Leave the queue listener of the Manager menu when the menu has not
been created; a queue started from here made it raise
- Add browser tests of the handler and of the menu listener
- Add a CHANGELOG entry
The same change for manager-v4 is #3526.