Upload metadata.ini

!0000-a1111-fix/metadata.ini

@@ -0,0 +1,55 @@
+[Extension]
+Name = 0000-a1111-fix
+
+; Notes:
+; - the real canonical name A1111 uses to match Before/After targets is
+;   always the lowercased FOLDER name, not the "Name =" field above.
+;   modules/extensions.py:ExtensionMetadata.__init__ reads "Name" and then,
+;   a couple of lines later, unconditionally overwrites it with the folder
+;   name -- so "Name =" here is documentation only, it has zero effect on
+;   matching. Rename the FOLDER, not this line, if you ever need to change
+;   how other extensions can reference this one.
+; - the "!0000-" folder prefix forces early alphabetical sort, but that only
+;   wins against other entries inside extensions/. A1111 scans
+;   extensions-builtin/ to completion before it ever looks inside
+;   extensions/ (modules/extensions.py:list_extensions), so a builtin
+;   extension is always earlier in the natural, unconstrained order no
+;   matter what this folder is named. The Before= lines below are what
+;   actually overrides that, via the topological sort in
+;   modules/scripts.py:list_scripts().
+; - Before/After targets are matched by EXACT, case-insensitive folder name.
+;   A non-matching name fails silently (no error, the edge is just never
+;   created) -- verify names against the real extensions/ and
+;   extensions-builtin/ directories instead of guessing. "canvas-zoom" used
+;   to be a guess here and did not match the extension actually shipped in
+;   this repo, which is named canvas-zoom-and-pan.
+; - "name1|name2|name3" (pipe, no surrounding spaces) picks whichever of the
+;   alternatives is actually installed and ignores the rest -- see
+;   modules/extensions.py:get_script_requirements. Used below for
+;   third-party extensions whose exact folder name can vary by how the user
+;   installed them.
+
+; javascript/fix.js
+; Kept for defense in depth, but not strictly load-bearing for FIX-1/2/3 as
+; currently written: they patch GLOBAL functions (scheduleAfterUiUpdateCallbacks,
+; executeCallbacks, inputAccordionChecked) by reassignment, and FIX-2
+; additionally re-wraps any callback queue right before it runs, regardless
+; of when things were registered. Both patterns only require fix.js to have
+; executed at all before DOMContentLoaded, which holds for any sync or defer
+; <script> tag no matter its position. Ordering would only matter if some
+; other extension captured a direct reference to the original function at
+; its own parse time instead of calling window.xxx(...) fresh on use --
+; uncommon, but the entries below cost nothing if unused.
+[javascript/fix.js]
+Before = sd-webui-tabs-extension|sd-webui-tabs-extension-main sd-webui-controlnet|sd-webui-controlnet-main canvas-zoom|sd-webui-canvas-zoom|canvas-zoom-and-pan
+
+; scripts/backend_watchdog.py
+; This one DOES need to run before other extensions' Python: it times each
+; extension's import as it happens, and it needs to be watching before an
+; import starts in order to catch a slow or stuck one live. Builtin
+; extensions are otherwise unreachable by any folder-naming trick (see
+; note above), so they are listed explicitly and exhaustively -- this is
+; every folder currently under extensions-builtin/ in this repo. Add to
+; this list if a future A1111 version ships additional builtin extensions.
+[scripts/backend_watchdog.py]
+Before = ldsr lora scunet swinir canvas-zoom-and-pan extra-options-section hypertile mobile postprocessing-for-training prompt-bracket-checker soft-inpainting