zero01101 / openOutpaint

local offline javascript and html canvas outpainting gizmo for stable diffusion webUI API 🐠
MIT License
500 stars 43 forks source link

[Bug]: Error generating images #267

Closed ghost closed 8 months ago

ghost commented 8 months ago

Is ths issue about the extension?

What happened?

when executing [dream] the cmd displays images being generated and the GPU reflect generation like usage. But the images does not arrive to the UI, a error with the text "Error generating images" appears at the bottom right.

Steps to reproduce the problem

  1. Go to openOutpaint tab
  2. Press dream and click anywhere in the screen

What should have happened?

Image should have been displayed

Commit where the problem happens

a4a0200f

What platforms do you use to access openOutpaint?

Windows

What browsers do you use to access the UI ?

Mozilla Firefox, Google Chrome, Microsoft Edge

Browser Extensions/Addons

none

AUTOMATIC1111 webUI Commandline Arguments

--api

Additional information

Console: Screenshot 2023-10-28 192718 Network: Screenshot 2023-10-28 211615

ghost commented 8 months ago

I reset my pc, and reinstalled automatic11111. Problem persist. Is this a known issue or is this the first rare approach someone has made about this?

zero01101 commented 8 months ago

disclaimer: apologies for the extended delay, my brain is terrible and you shouldn't expect much from me

try going to http://127.0.0.1:7860/docs#/default/text2imgapi_sdapi_v1_txt2img_post, click try it out and populate the request body input with

{
    "batch_size": 1,
    "cfg_scale": 7,
    "enable_hr": false,
    "height": 512,
    "n_iter": 1,
    "negative_prompt": "test",
    "prompt": "test",
    "restore_faces": false,
    "sampler_index": "DDIM",
    "seed": "1",
    "steps": 1,
    "width": 512
}

and execute it - it should return a base64 string if webUI's API is returning images successfully. check the a1111 console logs for errors as well beyond the browser's console

ghost commented 8 months ago

No worries, take your time if you have :).

this is the log after testing the suggested, image

The test, same outputput: image

zero01101 commented 8 months ago

sorry again for delayed responses; the fact that you're receiving the same error in bare API calls unfortunately confirms that your issue is within A1111 somewhere, likely some extension you may have installed as well... i'd suggest maybe disabling all 3rd party A111 extensions and re-enabling one by one until you find the one that's causing havoc with your API availability :/