Running webui.bat is updating numpy from 1.26.4 to 2.2.6, causing A1111 to fail

[sanfordandsonrc]

No updates recently, and today A1111 (webui.bat) is failing with the following error:

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.2.6 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.

If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.

A "pip list" command in my /venv/Scripts folder shows that the numpy version is 2.2.6, so, per google search, I uninstalled and downgraded numpy by using:

pip uninstall numpy

then:

pip install "numpy<2.0"

A "pip list" in the /venv/Scripts folder shows that the numpy version is now 1.26.4.

However, when I run webui.bat again to launch A1111, I get the same error shown above, and a "pip list" command reveals that the version of numpy is AGAIN set to 2.2.6.

How do I fix this issue?

Any help is appreciated.

[dawolf]

Same problem. I followed the steps to uninstall numpy and install numpy<2.0 and it did not resolve the issue.

pip uninstall numpy
pip install "numpy<2.0"

What I did after downgrading numpy:

Edit the file webui/webui-user.bat (for Windows) and add the launch option: --skip-install on the COMMANDLINE_ARGS line.

My webui-user.bat now has this line:

set COMMANDLINE_ARGS=--xformers --autolaunch --theme dark --skip-install

And webui starts at the moment. This skips the requirements checks at launch, so you should keep that in mind and maybe remove the --skip-install parameter in the future after this works again.

[sanfordandsonrc]

dawolf,

Made the change, and it seems to have gotten around the error with NumPy, but now I am having a problem with gradio. Getting the following error:

AttributeError: module 'gradio.components' has no attribute 'IOComponent'. Did you mean: 'Component'?

If you have a solution for that, it would be great. For now, I have installed Forge UI, and have abandoned A1111. Forge UI is working great, and is MUCH faster generating images! So, maybe A1111 crapping out is a GOOD thing!

[dawolf]

I did not run into the Gradio error, sorry no idea how to proceed there. Good to know that Forge works for you.

[w-e-w]

just now I performed a clean install and it seems to work fine
so likely there is an extension causing some dependency conflicts with base webui webui

if you wish to debug the issue I was suggest you first delete your current venv and and move everything in your extensions directory to some temporary directory

with venv deleted when you the next time you launch webui it should recreate the venv and bring you back to default version of web UI

then add back your extensions one by one by moving it from the temporary directory back into extensions directory and then relaunch webUI
most likely at some point the issue that you experience would occur, and you would know what extension might be the cause of the issue

I would suggest making a backup of venv before adding in extentions, this way if they error occurs you can quickly revert it back to a working state

after finding the extension that's causing the issue you can run pip freeze to see what package dose it install
or better use pipdeptree https://pypi.org/project/pipdeptree/ to see a tree of the dependencies and see what's causing the issue

if you don't know how to interpret the results you can share them and maybe people can come up with a fix