Closed cooperdk closed 1 year ago
FIX:
It seems that the Web UI did not upgrade requirements from requirements.txt when starting up. Gradio, among others, have been upgraded to 3.31.0 while it used to be 3.28.x.
So doing a pip install --upgrade -r requirements.txt
from venv solved the issue.
I am also getting this error. Are you sure the command you ran from the venv was pip upgrade
?
EDIT: confirmed the command is pip install --upgrade -r requirements.txt
I am also getting this error. Are you sure the command you ran from the venv was
pip upgrade
?
Sorry, I changed it just above. It's of course pip install --upgrade -r requirements.txt
BTW, the issue is really, why doesn't the webui match the current releases with the requirements file? There are even Python modules to handle this.
@cooperdk
requirements_versions.txt
is the locked-version requirements file this repo uses; if you install everything from requirements.txt
, you may get incorrect (untested) versions of dependencies.launch.py
does normally attempt to install versions from requirements_versions.txt
. You're not showing the entire log, so I can't tell why it's not doing that for you.There was no information on any kind of completed updated for the main webui.
But to put it short, upgrading gradio did work. There must therefore be a mistake in the upgrade test function.
Hent BlueMail til Android
Den 28. maj 2023 15.03, fra 15.03, Aarni Koskela @.***> skrev:
@cooperdk
requirements_versions.txt
is the locked-version requirements file this repo uses; if you install everything fromrequirements.txt
, you may get incorrect (untested) versions of dependencies.launch.py
does normally attempt to install versions fromrequirements_versions.txt
. You're not showing the entire log, so I can't tell why it's not doing that for you.-- Reply to this email directly or view it on GitHub: https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/10758#issuecomment-1566134758 You are receiving this because you were mentioned.
Message ID: @.***>
Glad you found a workaround, anyhow. Closing.
Is there an existing issue for this?
What happened?
This error occurs after configuration of extensions, right before opening the socket for HTTP access.
Steps to reproduce the problem
What should have happened?
The UI should have started.
Commit where the problem happens
20ae71f
What Python version are you running on ?
Python 3.10.x
What platforms do you use to access the UI ?
Windows
What device are you running WebUI on?
Nvidia GPUs (RTX 20 above)
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
List of extensions
Console logs
Additional information
This error did NOT occur right before updating to the 1.3.0 release.