-
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
add test-invoke-pip.yml #1521
add test-invoke-pip.yml #1521
Conversation
since it requires to have torch already installed also restore origin requirements-base.txt after suc. test in my fork
This comment is obsolete now 🙈
|
I don't know all the ins and outs of pip dependency resolution, but the concern I would have about splitting it into multiple commands is whether or not it resolves things the same way when it's not given the dependency tree all at once. Especially when modifiers like The error looks like the one this was intended to fix: XPixelGroup/BasicSR#514 which is tagged as if it were released in basicsr 1.4.2. And yet, the logs here show this using 1.4.2 and encountering that error on line 8 of setup.py. The line removed by that PR??? |
I am not sure if I can follow you. The error appears for example here, which was when installing But yes, I am with you, if possible it would be better to have the |
Wait, how did it end up with 1.4.1? We have a requirement for 1.4.2, that's what it downloaded... oh.
[See the pip manual on Backtracking for why it's downloading so many versions.] So initially pip did get us the right version of basicsr, but then something has it going back a bunch of versions of realesrgan, until it finally goes back so far that it finds a realesrgan requiring the broken basicsr. What a mess! requirements-base currently doesn't specify a version dependency for realesrgan at all. Can we add one to prevent it from going back that far? It'll likely break, because there was some reason it thought it wouldn't be able to use the current version of realesrgan in the first place, but at least it will tell us what that reason is and maybe that's something we can fix. |
add `basicsr>=1.4.2` to requirements-base.txt remove second installation step
When I replace
|
informed @lstein that I need information about how to run |
Is or rather, I think you may be asking for all the options to be set on the command line, like |
This is why the requirements in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, but I think @tildebyte should check.
@mauwii is this ready for a merge, and will it fix the current CI errors? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ugly, but there are now three scripts that call the same codebase: preload_models.py
, load_models.py
, and configure_invokeai.py
. I really only want to have the last one, but I don't want to alter the CI files without @mauwii 's blessing.
I'm getting the following dependency error after running
|
Are you using a clean environment? I mean the runners work to do the installation, so I doubt that there is any requirements error at all .... |
And the runners succeed even with python 3.9 and python 3.10 xD |
mostly suspiccious to me is this when you are using a clean and new .venv, this should be the python3 path to your venv and i doubt that you created this in Also strange is from where the |
I go away for a few days... Why was this done, pip install -r requirements....txt was successfully installing a working InvokeAi before this change. |
For me on mac with M1 it didn't, neither for lstein, neither for the Runners.... So it was implemented to fix the Installation and it was discussed here and in discord. But nobody would stop you from implementing |
So basically your saying you broke the pip install cos the conda install is broken ??? I'd love to fix it but conda is not getting anywhere near any computer I have to use python on. |
The Conda fix was implemented after the pip fix and has nothing to do with the pip fix. Maybe you should re-read what I wrote, which was speaking about the pip install which you mentioned... |
because the pip install was broken. You can see this PR went through a lot of runs trying to find something that worked: https://github.com/invoke-ai/InvokeAI/actions/workflows/test-invoke-pip.yml?query=branch%3Aadd-test-invoke-pip-workflow+event%3Apull_request |
I don't know when it doesn't work for the guys I've been using it right from the beginning. |
I wonder if its because you took out the prefer binary option |
So I guess you did not try a Installation from a clean venv, which indeed did not work. I did not spend hours of my life to fix something which is not broken, just for fun or to break it for everybody....
just take a look at the history, there are more than enough failing runs where you could look at .... |
Sorry, I know nothing about Github actions would know where to start |
Just edited the -e . back in on my own machine and i the pip went without issue. python -m venv InvokeAIPip edit equirements-mac-mps-cpu.txt pip install --prefer-binary -r requirements-mac-mps-cpu.txt |
Why do you do a pip install -e . when you have it edited back into the requirements? I would suggest you open a PR if it is working to install now with -e . in the requirements. as I say I was not the only person who was affected with problems, also the runners didn't manage to install, that is all I have to say here .... |
vBecause I clumsily copied an extra line from the script I used, the had a exit where I did the edit. % cat create_sd_stop.sh 1185 ./create_sd_stop.sh |
#1570 raised |
this workflow is similar to the conda test workflow, but instead is using pip to install requirements. It is testing
with Python 3.9 and 3.10.
IMPORTANT
this removes
-e .
from those 3 requirement files (imho should be removed from the others as well). So the workflow now is to install requirements, and afterwardspip install -e .