InvokeAI/docs/help/TROUBLESHOOT.md
Matthias Wild ec2dc24ad7
Mkdocs-material (#575)
* Squashed commit of the following:

commit 82d9c25d9a87ea5f6fbdb0445313e48cd8ae3035
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 19:29:11 2022 +0200

    fix branch name in mkdocs-flow

commit 2e276cecc1942050ae8b22f4a417c576c49763a1
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 19:28:35 2022 +0200

    fix theme name

commit 2eb77c1173598e161e8a5a9812b021b831363183
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 19:14:42 2022 +0200

    fixed some links and formating in main README

commit 66a7152e48e8c66c9286f47a6b088920a8fcdcd8
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 08:58:58 2022 +0200

    trigger mkdocs deployment on main

commit 897cc373ce4f9d18d8cb2837b5931c4b674c836b
Merge: 89da371 3b5a830
Author: 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

commit 3b5a8308eb6b7ee572ff07f78829f64bcf55b4d9
Author: 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

commit 0b4f5a926ff8aad1460e0be8093ee02d719a576d
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 07:41:45 2022 +0200

    update mkdocs config

commit 872172ea7008aa1217c1259c7ecab16ddafd1a0e
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 07:33:49 2022 +0200

    added the mkdocs-git-revision-date-plugin

commit eac81bf87588ec88b65f3415aa838c330fbd621b
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 06:46:43 2022 +0200

    add  prettier config
    remove markdownlint
    move and rename requirements-mkdocs.txt

commit b36d4cc088a49af56026aa2dd2e85d6bfb181bd1
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 02:06:39 2022 +0200

    add dark theme

commit a14f18fede6febccf1c117cba50a1aff1eac80a9
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 01:38:02 2022 +0200

    update mkdocs flow and config

commit 2764b48693ed382bc01a2cb7aab282dbf95cd9ee
Author: mauwii <Mauwii@outlook.de>
Date:   Wed Sep 14 01:15:33 2022 +0200

    add mkdocs workflow

commit 1bd22523b1a52ac24bc5f950debb450f903c2d51
Author: 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>
2022-09-15 10:53:41 -04:00

2.7 KiB

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.