[Bug]: Setting --data-dir to a path outside of the Gradio working directory breaks extensions. Commit: ea9bd9fc #7684
Labels
asking-for-help-with-local-system-issues
This issue is asking for help related to local system; please offer assistance
gradio
Items related specifically to Gradio (user interface library). May or may not be upstream issues.
Is there an existing issue for this?
What happened?
After installing an extension (in my case, a1111-sd-webui-tagcomplete), it fails to activate.
Instead, the following error is returned:
Steps to reproduce the problem
What should have happened?
Extension should have activated normally.
Commit where the problem happens
ea9bd9f
What platforms do you use to access the UI ?
Linux, Other/Cloud
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of extensions
a1111-sd-webui-tagcomplete
Console logs
Additional information
Ideally, i would want extensions to be stored outside the stable-diffusion-webui to survive container rebuilds.
This might not be possible though, as Gradio seems to enforce its directory requirements.
Also, possibly, not everybody would want to put their extensions in the same location as other user data.
An alternative would be, to decouple the directory given with --data-dir and the directory where the extensions are loaded from.
The text was updated successfully, but these errors were encountered: