Some problems I encountered when using the controlnet API

[wym19970515]

Problem 1:
The default json parameter setting will cause some errors (only some errors, but the interface can still work normally in fact)：


When I solve the problem of hr_upscale type error, there will be new error reports, which will not be listed here.

Problem 2 (serious):
The call of controlnet txt2img API (/controlnet/txt2img) will affect the original API (/sdapi/v1/txt2img and /sdapi/v1/img2img).
As long as the controlnet API has been used, the use of the original API will be abnormal, and the line draft which is generated by controlnet before will still take effect on the call of the original API. Even after calling the controlnet API, the txt2img and img2img of the web page will still be affected by the line draft generated by the previous controlnet API, even if the controlnet function is not enabled.

By the way, the call of the controlnet api will generate a large number of debug logs, so I want to know whether the log level of the interface can be adjusted ?

[wym19970515]

Picture for Problem 2:
The line draft I obtained through controlnet txt2img API (/controlnet/txt2img)：

After the controlnet API call, the image generated through web page when controlnet is not enabled：

Images generated many times can always fit with the line draft, and the time consumption is close to that of opening the controlnet function, so I think the online draft obtained through the control API is still valid at this time.

[Mikubill]

API args issue and network restore already fixed in recent commits.

[wym19970515]

Thanks