Ошибка there was an error loading script

Is there an existing issue for this?

• I have searched the existing issues and checked the recent builds/commits

What happened?

When I start webui-user.bat it shows this error:

Error loading script: two_shot.py
Traceback (most recent call last):
  File "C:stable-diffusion-webuimodulesscripts.py", line 248, in load_scripts
    script_module = script_loading.load_module(scriptfile.path)
  File "C:stable-diffusion-webuimodulesscript_loading.py", line 11, in load_module
    module_spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:stable-diffusion-webuiextensionsstable-diffusion-webui-two-shotscriptstwo_shot.py", line 16, in <module>
    from modules.script_callbacks import CFGDenoisedParams, on_cfg_denoised, on_after_ui
ImportError: cannot import name 'on_after_ui' from 'modules.script_callbacks' (C:stable-diffusion-webuimodulesscript_callbacks.py)

Steps to reproduce the problem

Update automatic1111 to latest and start webui-user.bat

What should have happened?

No error should show

Commit where the problem happens

Master

What platforms do you use to access the UI ?

Windows

What browsers do you use to access the UI ?

Google Chrome

Command Line Arguments

set COMMANDLINE_ARGS= --autolaunch --api --xformers --vae-path "modelsVAEvae-ft-mse-840000-ema-pruned.pt"

List of extensions

a1111-sd-webui-haku-img
a1111-stable-diffusion-webui-vram-estimator
batch-face-swap
clip-interrogator-ext
ddetailer
deforum-for-automatic1111-webui
depth-image-io-for-SDWebui
depthmap2mask
DreamArtist-sd-webui-extension
ebsynth_utility
enhanced-img2img
multidiffusion-upscaler-for-automatic1111
openOutpaint-webUI-extension
openpose-editor
sd-3dmodel-loader
sd-civitai-browser
sd-extension-steps-animation
sd-extension-system-info
sd-fractal-zoom
sd-webui-additional-networks
sd-webui-ar
sd-webui-controlnet
sd-webui-depth-lib
sd-webui-model-converter
sd-webui-riffusion
seed_travel
shift-attention
stable-diffusion-webui
stable-diffusion-webui-chatgpt-utilities
stable-diffusion-webui-composable-lora
stable-diffusion-webui-depthmap-script
stable-diffusion-webui-images-browser
stable-diffusion-webui-instruct-pix2pix
stable-diffusion-webui-prompt-travel
stable-diffusion-webui-Prompt_Generator
stable-diffusion-webui-two-shot
ultimate-upscale-for-automatic1111

Console logs

Already up to date.
venv "c:|stable-diffusion-webuivenvScriptsPython.exe"
Python 3.10.9 (tags/v3.10.9:1dd9be6, Dec  6 2022, 20:01:21) [MSC v.1934 64 bit (AMD64)]
Commit hash: 806aa5e8e7a9a6e9e8c213ecc539002b494e9f84
Installing requirements for Web UI
Installing requirements for Batch Face Swap




Installing requirements for scikit_learn

Installing requirements for Ebsynth Utility
Installing requirements for Ebsynth Utility





Initializing Riffusion




Installing imageio-ffmpeg requirement for depthmap script
Installing pyqt5 requirement for depthmap script



Launching Web UI with arguments: --autolaunch --api --xformers --vae-path modelsVAEvae-ft-mse-840000-ema-pruned.pt
*Deforum ControlNet support: enabled*
[AddNet] Updating model hashes...
0it [00:00, ?it/s]
[AddNet] Updating model hashes...
0it [00:00, ?it/s]
Error loading script: two_shot.py
Traceback (most recent call last):
  File "c:|stable-diffusion-webuimodulesscripts.py", line 248, in load_scripts
    script_module = script_loading.load_module(scriptfile.path)
  File "c:|stable-diffusion-webuimodulesscript_loading.py", line 11, in load_module
    module_spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "c:|stable-diffusion-webuiextensionsstable-diffusion-webui-two-shotscriptstwo_shot.py", line 16, in <module>
    from modules.script_callbacks import CFGDenoisedParams, on_cfg_denoised, on_after_ui
ImportError: cannot import name 'on_after_ui' from 'modules.script_callbacks' (c:|stable-diffusion-webuimodulesscript_callbacks.py)

Loading weights [e1441589a6] from c:|stable-diffusion-webuimodelsStable-diffusionSD_SDv1-5-pruned.ckpt
Creating model from config: c:|stable-diffusion-webuiconfigsv1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Loading VAE weights from commandline argument: modelsVAEvae-ft-mse-840000-ema-pruned.pt
Applying xformers cross attention optimization.
Textual inversion embeddings loaded(0):
Textual inversion embeddings skipped(3): 21charturnerv2, InkPunk768, InkPunkLandscapes768
Model loaded in 4.3s (load weights from disk: 2.1s, create model: 0.2s, apply weights to model: 0.3s, apply half(): 0.4s, load VAE: 0.2s, move model to device: 0.4s, load textual inversion embeddings: 0.7s).
3840 1600
1550
add tab
[VRAMEstimator] Loaded benchmark data.
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
Startup time: 28.9s (import gradio: 2.2s, import ldm: 1.4s, other imports: 1.8s, list extensions: 4.4s, load scripts: 3.4s, load SD checkpoint: 4.5s, create ui: 10.9s, gradio launch: 0.1s).

Additional information

It was working perfictly with 0 errors before pulling the last update, however I havent updated automatic1111 since few weeks ago.
Yester day I added git pull in the webui.bat and it did update and the error start showing.

The browser helps to track the loading of external resources, such as pictures, scripts and more.

Two primary events are used for that purpose:

• onload: it supposes a successful load.
• onerror: it means that an error has occurred.

Imagine that you should load a third-party script and call a function residing there, as illustrated below:

let script = document.createElement('script');
script.src = "script.js";
document.head.append(script);

To run the function declared inside that script, you should wait until the script loads and only then call it.

Please note, that here you could also use JavaScript modules, but they are not widely used by third-party libraries.

Script.onload

The load event is the main helper here. It occurs once the was already loaded and executed.

Here is an example of the load event:

So, Script variables and run functions can be used in download.

But, the loading may fail. Note that there isn’t any such script (error 404) or the server is done.

Let’s see what happens in such a circumstance.

Script.onerror

Errors occurring during the script loading are tracked in an error event.

Let’s take a look at an example of requesting a non-existing script:

Please, take into account that the details of the HTTP error are not available here: you can’t know whether it’s an error 404, 500 or anything else.

Another important thing to note: the onload and onerror events track only the loading itself. In other words, errors occurring during the script processing and execution are out of the framework. So, if a script loaded efficiently, then onload happens, even if it includes some programming errors. For tracking the script errors, you can use a global handler called window.onerror.

The load and error events operate for any other resources that have an external src, like in the example below:

But, note that several resources begin loading once they are added to the document. The <img> is an exception to the rule. It begins to load after getting a src (*).

For <iframe>, the iframe.onload event occurs once the iframe loading is over. It is both for the efficient load and in case of an error.

Scripts from one site don’t have access to the scripts of the other one. For example, a script at https://www.instagram.com/ can’t read the user’s mailbox at https://gmail.com.

In other words, one origin (domain/port/protocol) can’t access the content of the other one. Even in case of having a subdomain, these are considered different origins.

The rule above affects the resources from other domains, as well.
An example of a script error.js consisting of a single (bad) function call is demonstrated below:

//  error.js
noSuchFunction();

If you try loading it from the same site where it’s located, you will have this:

<script>
  window.onerror = function(message, url, line, col, errorObj) {
    alert(`${message}n${url}, ${line}:${col}`);
  };
</script>
<script src="/article/onload-onerror/crossorigin/error.js"></script>

A good error report can be seen here:

Uncaught ReferenceError: noSuchFunction is not defined
https://javascript.info/article/onload-onerror/crossorigin/error.js, 1:1

The example of loading the same script from another domain will look like this:

<!DOCTYPE html>
<html>
  <head>
    <title>Title of the Document</title>
  </head>
  <body>
    <script>
      window.onerror = function(message, url, line, col, errorObj) {
        alert(`${message}n${url}, ${line}:${col}`);
      };
    </script>
    <script src="https://cors.javascript.info/article/onload-onerror/crossorigin/error.js"></script>
  </body>
</html>

So, there is a different report here:

Script error.
, 0:0

There can be different details, depending on the browser. However, idea remains the same: any information regarding the internals of a script is hidden. The reason is that it is from a different domain.

Still, it is important to know details about errors.

There are services, listening for global errors using window.onerror, saving errors and providing an interface to access and analyze them. So, they make it possible to see real errors, triggered by the users. But, if a script has another origin, no more information will be available.

For allowing cross-origin access, the <script> tag should have the crossorigin attribute. The remote server has to provide specific headers.

Three levels of cross-origin access exist:

1. No crossorigin attribute — the access is not allowed.
2. For crossorigin="anonymous" the access is allowed, in case the server responds with the header Access-Control-Allow-Origin including or the origin. Any authorization information or cookies are sent to the remote server.
3. crossorigin="use-credentials": the access is allowed in case the server sends back the Access-Control-Allow-Origin header with the origin and Access-Control-Allow-Credentials: true. Authorization information and cookies are sent to the remote server.

In case of not having any crossorigin attribute, the access will be prohibited.

So, let’s see how to add it.

You can choose between "anonymous" and "use-credentials".
In the event of not caring about the cookies, "anonymous" is the way to go, like this:

<!DOCTYPE html>
<html>
  <head>
    <title>Title of the Document</title>
  </head>
  <body>
    <script>
      window.onerror = function(message, url, line, col, errorObj) {
        alert(`${message}n${url}, ${line}:${col}`);
      };
    </script>
    <script crossorigin="anonymous" src="https://cors.javascript.info/article/onload-onerror/crossorigin/error.js"></script>
  </body>
</html>

Supposing that the server provides Access-Control-Allow-Origin header, the full error report is ready.

Resources such as scripts, styles, images provide load and error events for tracking their loading:

• The load event happens on a successful load.
• The error event occurs on a failed load.

, there is an exception: <iframe>, which only triggers the load, for each load completion, even if the page is not found. For resources, you can also use the readystatechange event. But it is used rarely as the load and error events are simpler and handier.