Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Extentions don't always detect properly #261

Open
Kadah opened this issue Sep 3, 2023 · 1 comment
Open

[Bug]: Extentions don't always detect properly #261

Kadah opened this issue Sep 3, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Kadah
Copy link

Kadah commented Sep 3, 2023

What happened?

There might be a bug with extension detection. Have noticed that the two existing extensions supported don't always gets detected/enabled each reload, and mine is exhibiting the same behavior. Usually all 3 will become enabled after 1-2 extra reloads

Steps to reproduce the problem

  1. Have A1111 running with Dynamic Prompts and ControlNets (and CFG Rescale if using my PR)
  2. Load openOutpaint (either as extension or standalone)
  3. Expand Extensions
  4. Wait to see if all extentions become enabled
  5. Observe that on some loads, not all extensions are enabled
  6. Reload, try again

What should have happened?

All supported extensions should enabled each load when installed and active on A1111.

Commit where the problem happens

2f3c65e

What platforms do you use to access openOutpaint?

Linux

What browsers do you use to access the UI ?

Google Chrome

Browser Extensions/Addons

None active on openOutpaint

AUTOMATIC1111 webUI Commandline Arguments

--no-half-vae --api --opt-split-attention --cors-allow-origins=http://127.0.0.1:7860,http://127.0.0.1:3456 --no-download-sd-mode

Additional information

Hadn't touched any of the extension support before looking in to adding cfg rescale support for #260. I had a look to see if I could figure out the cause, but my JS is extremely rusty.

@Kadah Kadah added the bug Something isn't working label Sep 3, 2023
@zero01101
Copy link
Owner

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

i've never had controlnet/dynamic prompts not detect properly myself, but it's likely something is indeed broken with extension support because it's extra jank as mentioned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants