ec2dc24ad7
* Squashed commit of the following: commit82d9c25d9aAuthor: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 19:29:11 2022 +0200 fix branch name in mkdocs-flow commit2e276cecc1Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 19:28:35 2022 +0200 fix theme name commit2eb77c1173Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 19:14:42 2022 +0200 fixed some links and formating in main README commit66a7152e48Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 08:58:58 2022 +0200 trigger mkdocs deployment on main commit897cc373ceMerge:89da3713b5a830Author: Matthias Wild <40327258+mauwii@users.noreply.github.com> Date: Wed Sep 14 07:51:23 2022 +0200 Merge pull request #1 from mauwii/mkdocs Mkdocs commit3b5a8308ebAuthor: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 07:42:56 2022 +0200 huge update I was pretty busy trying to make the Readmes / docs look good in MkDocs commit0b4f5a926fAuthor: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 07:41:45 2022 +0200 update mkdocs config commit872172ea70Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 07:33:49 2022 +0200 added the mkdocs-git-revision-date-plugin commiteac81bf875Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 06:46:43 2022 +0200 add prettier config remove markdownlint move and rename requirements-mkdocs.txt commitb36d4cc088Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 02:06:39 2022 +0200 add dark theme commita14f18fedeAuthor: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 01:38:02 2022 +0200 update mkdocs flow and config commit2764b48693Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 01:15:33 2022 +0200 add mkdocs workflow commit1bd22523b1Author: mauwii <Mauwii@outlook.de> Date: Wed Sep 14 00:57:37 2022 +0200 I already begun with formating / revising the sites * change repository in mkdocs config to lstein * adapt changes from repos main README.md Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com>
2.7 KiB
title
| title |
|---|
| F.A.Q. |
Frequently-Asked-Questions
Here are a few common installation problems and their solutions. Often these are caused by incomplete installations or crashes during the install process.
QUESTION
During conda env create -f environment.yaml, conda hangs indefinitely.
SOLUTION
Enter the stable-diffusion directory and completely remove the src directory and all its contents.
The safest way to do this is to enter the stable-diffusion directory and give the command
git clean -f. If this still doesn't fix the problem, try "conda clean -all" and then restart at
the conda env create step.
QUESTION
dream.py crashes with the complaint that it can't find ldm.simplet2i.py. Or it complains that
function is being passed incorrect parameters.
SOLUTION
Reinstall the stable diffusion modules. Enter the stable-diffusion directory and give the command
pip install -e .
QUESTION
dream.py dies, complaining of various missing modules, none of which starts with `ldm``.
SOLUTION
From within the stable-diffusion directory, run conda env update -f environment.yaml This is
also frequently the solution to complaints about an unknown function in a module.
QUESTION
There's a feature or bugfix in the Stable Diffusion GitHub that you want to try out.
SOLUTION
Main Branch
If the fix/feature is on the main branch, enter the stable-diffusion directory and do a
git pull.
Usually this will be sufficient, but if you start to see errors about missing or incorrect modules, use the command
pip install -e . and/or
conda env update -f environment.yaml
(These commands won't break anything.)
Sub Branch
If the feature/fix is on a branch (e.g. "foo-bugfix"), the recipe is similar, but do a
git pull <name of branch>.
Not Committed
If the feature/fix is in a pull request that has not yet been made part of the main branch or a feature/bugfix branch, then from the page for the desired pull request, look for the line at the top that reads "xxxx wants to merge xx commits into lstein:main from YYYYYY". Copy the URL in YYYY. It should have the format
https://github.com/<name of contributor>/stable-diffusion/tree/<name of branch>
Then go to the directory above stable-diffusion and rename the directory to "stable-diffusion.lstein", "stable-diffusion.old", or anything else. You can then git clone the branch that contains the pull request:
git clone https://github.com/<name of contributor>/stable-diffusion/tree/<name of branch>
You will need to go through the install procedure again, but it should be fast because all the dependencies are already loaded.