Skip to content

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

Description

@Kadah

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions