InvokeAI: Error thrown running `dream.py` on main branch `ModuleNotFoundError: No module named 'ldm'`

When trying to run the dream.py file on the current main branch, I get the following error:

/content/stable-diffusion# pipenv run scripts/dream.py
Traceback (most recent call last):
  File "scripts/dream.py", line 12, in <module>
    import ldm.dream.readline
ModuleNotFoundError: No module named 'ldm'

Environment: Google Colab & Docker (WSL2 + GPU passthrough) Python 3.8.13

The error that was outputted above came from the google colab environment on the main branch (removed line that checked out a specific tag).

I’ve been working in a docker container and thought maybe it had something to do with not using conda, but I tried the colab notebook in the Colab env, and removed the line to checkout the specific tag, and encountered the same error, so I am fairly certain it’s an issue with the current branch rather than an env issue.

When I ran the same line on tags/release-1.09, it showed the initialization message

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 2
Comments: 29 (10 by maintainers)

Most upvoted comments

The original problem happens because conda adds the current path to PYTHONPATH. You can fix the error with:

PYTHONPATH=. python scripts/dream.py --full_precision

fserb on Sep 2, 2022

Well, it got you 50% of the way there…

Some other things to try:

Have you tried putting the full path to stable-diffusion in the environment variable PYTHONPATH?
Edit the file dream.py and put this at or near the top of the file:

sys.path.append(‘/path/to/stable-diffusion’)

(replace with the actual path to the stable-diffusion directory)

Let me know if you find a working solution. This has probably been the most elusive of bugs in the fork, and I wish I could get to the bottom of it.

Lincoln

On Wed, Aug 31, 2022 at 11:16 PM Mark V @.***> wrote:

I retried -e on my docker container just to make sure I didn’t do something big dumb, but same result

— Reply to this email directly, view it on GitHub https://github.com/lstein/stable-diffusion/issues/272#issuecomment-1233687078, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3EVKIWF2A26TPJUH6EEDV4AN2HANCNFSM6AAAAAAQB5MCAA . You are receiving this because you commented.Message ID: @.***>

–

Lincoln Stein

Head, Adaptive Oncology, OICR

Senior Principal Investigator, OICR

Professor, Department of Molecular Genetics, University of Toronto

Tel: 416-673-8514

Cell: 416-817-8240

@.***

E**xecutive Assistant

Michelle Xin

Tel: 647-260-7927

@.*** @.**>

Ontario Institute for Cancer Research

MaRS Centre, 661 University Avenue, Suite 510, Toronto, Ontario, Canada M5G 0A3

Collaborate. Translate. Change lives.

This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization.

lstein on Sep 1, 2022

The fixed colab works well thank you!

Bendito999 on Sep 10, 2022

My PR #422 was just merged to development branch, until development is merged to main, colab shortcut will redirect to previous version, please use this link in the meantime.

https://colab.research.google.com/github/lstein/stable-diffusion/blob/development/Stable_Diffusion_AI_Notebook.ipynb

artmen1516 on Sep 7, 2022

https://github.com/lstein/stable-diffusion/releases/tag/release-1.13

That’s the plan going forward.

tildebyte on Sep 6, 2022

@artmen1516;

In the previous pointer commit there were changes made to the requirements.txt file which installed all dependencies correctly

Yes, that is the case - I don’t know how that happened. Your advice for checking out a different commit is sound. Note that we’re still trying to figure out what ‘requirements.txt’ should contain, and recently in f4004f6 (merged to ‘development’) split it per-platform (so for e.g. for Colab it would be ‘requirements-lin.txt’)

tildebyte on Sep 6, 2022

Hey @Bendito999 @vanakema, I made the colab notebook, I just noticed that it is failing, this is because the repo owners changed where the tag release-1.09 was pointing when I made the notebook… I made it checkout to this tag since there were a lot of changes being made on real time and sometimes it worked correctly and other times it didn’t, so to avoid errors I decided to use an stable tag.

Based on my analysis, this is where it is pointing now, and where it was then.

Tag	release-1.09
Current pointer	81cbcb9
Previous pointer	4d72644

Let me know if i’m right @tildebyte @lstein

In the previous pointer commit there were changes made to the requirements.txt file which installed all dependencies correctly. Newer tags have issues with the dependencies which are still not resolved. You could checkout to the previous commit that tag 1.09 was using.

Use this notebook in my fork where i do what I explain, it is working as it used to… artmen1516/stable-diffusion/blob/colab-notebook-fix/Stable_Diffusion_AI_Notebook.ipynb

I don’t want to open a PR with this as a solution, since is not the best to use an specific commit, I will work to make it work with the lastest release, but in the meantime, this is a workaround to use the notebook.

Note: I didn’t use conda since I understand that conda takes a lot more memory and hence installation time, and the point with the notebook is to have something relatively fast to test the repo.

artmen1516 on Sep 6, 2022