[Bug]: ControlNet checkbox grayed out in Reforge

[fish-face]

What happened?

I am using Reforge (commit 037b6482) and I can't enable ControlNet in openOutpaint:

I am using the SD-webui version of openOutpaint and generation etc seems all to be working fine.

I didn't find any instructions on how to enable ControlNet within openOutpaint so I'm guessing it's supposed to be easy, but it's not possible here. I would guess that this is because Reforge does not use the regular Controlnet extension but has its own inbuilt version. Unfortunately this means that the normal version is automatically disabled and not usable. I'm wondering/hoping if it will just be a matter of checking for the presence of Reforge's alternate extension.

Steps to reproduce the problem

1. Install Reforge & enable --api
2. Install openOutpaint extension from the Extensions tab
3. Enable integrated ControlNet in the txt2img tab
4. Go to openOutpaint tab, see that "ControlNet" is disabled

What should have happened?

It would be enabled

Commit where the problem happens

3449ae8559c0f270d49ceb3ef7234f62feaac675

What platforms do you use to access openOutpaint?

Linux

What browsers do you use to access the UI ?

Mozilla Firefox

Browser Extensions/Addons

N/A

AUTOMATIC1111 webUI Commandline Arguments

--api --listen --enable-insecure-extension-access

Additional information

No response

[fish-face]

Hmm OK, after some investigation I think this is more of a feature request. I did some investigation and Forge's controlnet extension is somewhat different than the normal one. Indeed, I can't actually use the normal controlnet extension if I manually reenable it and disable the integrated one - I get torch errors.
I can bypass and rework some of the openOutpaint checks (e.g. there is no version endpoint so I just checked if anything was returned from model_list) and the checkbox is enabled and I can see the list of preprocessors and models. However, selecting inpaint models which (using the integrated extension) do work in img2img inpaint, don't seem to exert any guidance in openOutpaint. I'm guessing the way controlnet is invoked is different and it's just not being used at all.

As I said I manually switched back to the original extension and tried that, too, but I don't think it'll work. To enable it, you have to comment out forge's blacklist contained in modules_forge/config.py and then, in extensions, disable all of forge's built in ones and reenable the original. Doing this though, and again tweaking the checks in openOutpaint to not filter anything out, using the inpaint models results in an error on the commandline (it's not successfully parsed as JSON by openOutpaint so doesn't show up in the browser console) from controlnet saying that controlnet failed to use the VAE, and suggesting to use --no-half-vae or --no-half. These options do nothing in forge as it automatically works out how to load models.

Thus I think for this extension to work with Forge, it needs to support Forge's built-in extension.