-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
awaiting-responseWaiting for the issuer to respondWaiting for the issuer to respondbugSomething isn't workingSomething isn't working
Description
Has this issue been opened before?
Describe the bug
Entrypoint for auto installs dependencies for all existing extensions on disk not checking whether it is enabled.
My cat is left intact.
Which UI
auto or auto-cpu
Hardware / Software
Potato on steroids.
Steps to Reproduce
- Install any extension that has dependencies inside @install.py@ file.
- Disable that extension in webui.
- Restart container.
- See dependency installation info for that very extension being processed.
Additional context
Following code in services/AUTOMATIC1111/entrypoint.sh file is reason for such behavior:
# For install.py, please refer to https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Developing-extensions#installpy
list=(./extensions/*/install.py)
for installscript in "${list[@]}"; do
PYTHONPATH=${ROOT} python "$installscript"
done
I propose something like this to resolve if extension is enabled by using info in config.json file:
EXTNAME=`echo $installscript | cut -d '/' -f 3`
if ! `jq -e ".disabled_extensions|any(. == \"$EXTNAME\")" config.json`; then
PYTHONPATH=${ROOT} python "$installscript"
fi
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
awaiting-responseWaiting for the issuer to respondWaiting for the issuer to respondbugSomething isn't workingSomething isn't working