invoke-ai
Lstein release candidate 2.2.5
- Update requirements file to correct a clash between numpy and numba.
- Fix update scripts in preparation for 2.2.5. Tested on Linux and Windows, not Macintosh
@blessedcoolant @lstein should we just release this alongside model manager and translations?
Translations is in 2.2.5 but the model manager is not. @blessedcoolant suggested that the model manager go into 2.2.6, followed by diffusers in 2.3.0. I haven't played with the model manager yet so can't comment on its stability; I've been working on dev/diffusers.
On Sun, Dec 25, 2022 at 6:19 PM Kent Keirsey @.***> wrote:
@blessedcoolant https://github.com/blessedcoolant @lstein https://github.com/lstein should we just release this alongside model manager and translations?
— Reply to this email directly, view it on GitHub https://github.com/invoke-ai/InvokeAI/pull/2137#issuecomment-1364752570, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3EVJ2GNIDHVHKLCYVI6TWPDI7FANCNFSM6AAAAAATJDH7YI . You are receiving this because you were mentioned.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.
Model Manager still needs some refinement unless we finish it today which I don't think we can. So maybe for the next double point release.
Hello. I wish to let you know that I downloaded the Update-2.2.5.zip file from the Pre-release page of the 2.2.5-rc1 and ran it apparently without getting any error message, really a clean update. But, when I started the application with invoke.bat and then the Web UI at http:/127.0.0.1:9090 I got the same UI as of version 2.2.4 without the new Canvas and without any localization choice (no icon in the UI). In fact, checking inside the \frontend directory there is no \public folder which should contain the localization files. It seems like the update was still relying upon the 2.2.4 data. Hope I was able to explain myself. Thank you.
Model Manager still needs some refinement unless we finish it today which I don't think we can. So maybe for the next double point release.
Update. Turns out I did finish it today. Need to run some final testing and bug fixes. We can do it for 2.2.5 or maybe a quick 2.2.6 release in a few days.
Hello. I wish to let you know that I downloaded the Update-2.2.5.zip file from the Pre-release page of the 2.2.5-rc1 and ran it apparently without getting any error message, really a clean update. But, when I started the application with invoke.bat and then the Web UI at http:/127.0.0.1:9090 I got the same UI as of version 2.2.4 without the new Canvas and without any localization choice (no icon in the UI). In fact, checking inside the \frontend directory there is no \public folder which should contain the localization files. It seems like the update was still relying upon the 2.2.4 data. Hope I was able to explain myself. Thank you.
Same for me
After running again the update.bat for v2.2.5 I noticed that at a certain point it looks for the latest.zip file but he finds a cached version (where? Locally on my PC or remotely on the Github repository?) and it doesn't seem to effectively copy new files. Looking at the available Releases, the "latest" tag is assigned currently to the 2.2.4 version, which make sense because it's the "latest" official release, while v2.2.5 is still a Release Candidate. So, perhaps, the missing files updating is not wrong or a bug. I am attaching the entire console messages of my third run of update.bat for your information and reference, in case it might help. invokeai_2.2.5_update_bat_console.txt
Hope you won't kill me for all these comments, but I really want to help to make the 2.2.5 version a nice experience for users to install/update it. Probably, I am talking without proper knowledge of how this program works, in this case forgive me and let me know, I will make a step back.
That said, I decided to dig into this update (and install) problem with the Release Candidate 2.2.5 and here follow my findings at the moment.
I made an entire copy of my local installation in C:\InvokeAI into C:\TEMP and then I checked the content of the install.bat file inside the InvokeAI-installer-2.2.5-p1-windows.zip file and noticed that at line 18 it still refers to version 2.2.4, so I changed that link to
set INVOKE_AI_SRC=https://github.com/invoke-ai/InvokeAI/archive/refs/tags/2.2.5-rc1.zip
Then I ran the install.bat file and choose the C:\TEMP directory as the location for the installation of InvokeAI. Everything seemed to be going fine but at the end, after launching the web server, the UI still displayed the 2.2.4 interface (no localization icon and new beta canvas).
Then, I decided to try to use the suggested Update-2.2.5.zip file and examining its content, at line 13 it states "For example '.\update.bat v2.2.5' for release 2.2.5.", so I ran
c:\TEMP\InvokeAI>.\update.bat 2.2.5-rc1
and after the process completed I got this message:
InvokeAI has been updated to '2.2.5-rc1'
"Press any key to continue"
I started the web server running invoke.bat but, again, opening the URL in the web browser I am still getting the 2.2.4 UI. I also tried to Reset the Web Interface, but without any results.
In fact, in both above cases the \frontend directory is missing the \public folder and related \locales (as an example). I am a little confused and possibly I am doing something wrong, sorry if I am bothering you.
Furthermore, may I suggest you to display somewhere in the Web UI the version of InvokeAI that's running? It would be useful.
Thank you again for your patience.
I'm facing the same issue. The new UI toggle is not visible even after resetting the web ui. Also the version below the icon would be super helpful.
I need to update the update.sh script. It is pulling the old version. I
am currently on family holiday, and will make the update as soon as I’m
able. May not be till tomorrow.
L
On Tue, Dec 27, 2022 at 1:18 PM Kent Keirsey @.***> wrote:
@lstein https://github.com/lstein would the update process pull the new frontend build?
— Reply to this email directly, view it on GitHub https://github.com/invoke-ai/InvokeAI/pull/2137#issuecomment-1366088586, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3EVMDIGIB2QQP2U5PFBDWPMXHDANCNFSM6AAAAAATJDH7YI . You are receiving this because you were mentioned.Message ID: @.***>
-- Written on my cell phone. Anything that seems odd is the fault of auto-correct.
I’ll fold it into 2.2.5 as soon as I have a stretch of time. I’m in the midst of a family holiday now and do not have as much free time as I expected.
On Mon, Dec 26, 2022 at 10:28 AM blessedcoolant @.***> wrote:
Model Manager still needs some refinement unless we finish it today which I don't think we can. So maybe for the next double point release.
Update. Turns out I did finish it today. Need to run some final testing and bug fixes. We can do it for 2.2.5 or maybe a quick 2.2.6 release in a few days.
— Reply to this email directly, view it on GitHub https://github.com/invoke-ai/InvokeAI/pull/2137#issuecomment-1365250050, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3EVNB4YDRTD22MMOXC4LWPG2RJANCNFSM6AAAAAATJDH7YI . You are receiving this because you were mentioned.Message ID: @.***>
-- Written on my cell phone. Anything that seems odd is the fault of auto-correct.
Lgtm - lot of changes though. Let’s keep an eye on installer issues post release