Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building ldm environment on M1 Pro never ends #310

Closed
heurihermilab opened this issue Sep 2, 2022 · 5 comments
Closed

Building ldm environment on M1 Pro never ends #310

heurihermilab opened this issue Sep 2, 2022 · 5 comments

Comments

@heurihermilab
Copy link

Environment: MBP 14", M1 Pro, 16GB, latest OS, running miniforge with a base of Python 3.10.6. Ran conda clean and reset while debugging.

I am following the instructions in README-Mac-MPS.md with little success. This is unlike the installation I did yesterday, which just worked, so it's likely a configuration issue.

What happens is after executing

CONDA_SUBDIR=osx-arm64 conda env create -f environment-mac.yaml

the process never completes.

interestingly, whenever I've lost patience (T up to 2 hours) and ctrl-Z the process (and, later, kill -9 it), the following is returned:

Stopped                 ( __add_sys_prefix_to_path; "$CONDA_EXE" $_CE_M $_CE_CONDA "$@" )

A quick search of the folder doesn't turn up CONDA_EXE anywhere in the code, perhaps that's a hint. My Conda-fu is weak.

I'm likely to try out "Switch to regular pytorch channel and restore Python 3.10 for Macs. (#301)" next in the debugging process, as my previous installation ran 3.10 well enough for txt2img.py, though dream.py didn't seem to work.

@ideologysec
Copy link

Try this: #63 (comment)

@outcassed
Copy link

outcassed commented Sep 2, 2022

this happens when pip is waiting for user input to confirm overwriting files

instead of CONDA_SUBDIR=osx-arm64 conda env create -f environment-mac.yaml

try

PIP_EXISTS_ACTION=w CONDA_SUBDIR=osx-arm64 conda env create -f environment-mac.yaml

@heurihermilab
Copy link
Author

Many thanks for the suggestions and pointers. I'll keep these in mind and integrate info from other threads when I proceed later today.

@heurihermilab
Copy link
Author

Success! I followed the instrux from #315 with no trouble.

I'm running into the cannot import name 'TypeAlias' from 'typing' issue with both dream.py and txt2img.py, but I think the current problem may be resolved.

@magnusviri
Copy link
Contributor

TypeAlias is being discussed here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants