-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
latest environment.yaml does not result in functional env #63
Comments
I forked this repo a couple hours ago on a fresh machine (win10). Everything worked as expected. |
Huh. I did a fresh install a few days ago and it was working ok. Haven't changed environment.yaml for quite a while, but I'll take a look. |
tested today, running |
Same issue as @Zincr0. Happens with all Stable Diffusion repositories, unable to install at all. |
I suspect it's related to the wrongly closed bug conda/conda#10807 |
And i was thinking it's only me. Yesterday everything worked perfectly, i was just cleanining my env for something and becasue it been frozen i was thinking i'm doing something wrong. Edit: just tried the version from yesterady and it worked there. |
Could you attach the working version in a comment? I'd like to test it here, but am not sure which commit you're using. |
Any idea how to do this if I didn't use git clone but just downloaded it zipped via the web hitting the green button? |
You can workaround this by aborting the install when it hangs at "installing pip dependencies", and then installing each pip dependency manually (the ones listed on environment.yaml) |
if it's hanging because pip is trying (silently) to prompt you "this path already exists; should I overwrite it?" (i.e. conda/conda#10807), then try setting PIP_EXISTS_ACTION=w conda env create -f environment.yml |
the problem is probably that you already have one of these directories:
created by a previous installation attempt. so, pip's like "hey there's already a file there; what should I do?" you could probably solve this by running |
I got through the endless |
OK! i have managed to solve it, here's what worked for me: Cool, now when i'm synced with everyone i can also start making pull requests |
Nice! I’ll add that to the README this weekend when I do the documentation
update.
Lincoln
On Fri, Aug 26, 2022 at 2:58 PM Yuval Starnes ***@***.***> wrote:
OK! i have managed to solve it, here's what worked for me:
as Birch-san said, first of all, make sure you not having any useless
files by hitting
git clean -f
Then clean conda using:
conda clean -all
and that's it, install the enviroment and your'e rady to go.
Cool, now when i'm synced with everyone i can also start making pull
requests
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3EVMJXWW3ZTY2JRAAS4DV3EHW5ANCNFSM57PAH56Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Written on my cell phone. Anything that seems odd is the fault of
auto-correct.
|
I just tried to run the solution on a new wsl2 "vm" with a fresh miniconda install using the provided environment.yaml and upon running
python script/dream.py
I get the usual load model but after that everything stop without any error...Yes, I renamed the env from ldm to sdbm because I have too many repos I play with and they all use the same "ldm" name and this does not work well with conflicting requirements fort each... so I renamed the env in the environment.yaml file to make them per "repo".
If I then load my previous conda env with the original build from a fews days ago environment.yaml all is fine... Not sure what is missing but something is causing things to not work with the current yaml.
When it work under my previous ldm2 env I get e line about setting up the sampler that does not get shown with the latest commit:
The text was updated successfully, but these errors were encountered: