-
Notifications
You must be signed in to change notification settings - Fork 22
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
[bug] Extension seems incompatible with TheLastBen's Colab webui instance #11
Comments
Hi, actually, it seems someone was able to run this on colab, although as an extension: #6 not sure how. @Lesteriax, did you use a publicly available notebook for stable diffusion webui? |
Hi @seijihariki, I'm actually using paperspace gradient notebook, not colab, my mistake sorry. The fix happened as follows: I removed --gradio-debug (not sure where this would be found in other notebooks) I would basically launch the webui to get the link and then add it in userbat and refresh |
Makes sense, thanks for your input! @jvoxel, would you be able to provide us the notebook you used for this error to crop up? Mostly to investigate the issue further. |
A similar issue seems to have cropped up on another user of thelastben's colab. As this seems to be extension related, will move this issue to the extension's repo and mark the other issue as duplicate. |
So, instructions for reproducing this bug were provided by @createperhaps on #10:
The notebook seems to live at https://github.com/TheLastBen/fast-stable-diffusion. Will try to reproduce this later today. I'm centralizing discussion on this problem in this issue here. |
Thanks @seijihariki, let me know if you have any questions if anything is unclear. I didn't try to reinstall all of Automatic/SD (given it is more widespread, I doubt that would fix it), though I did restart the collab instance and it didn't sort itself out. I also tried to see if I could run the cor command and see if I could run it from https://zero01101.github.io/openOutpaint/ but I am not super familiar with Python. |
TheLastBen offers two servers, I am using the gradio checkbox if that makes a difference. |
Is there a way for us to see the “Internal Server Error” you are getting? If you could help us with a screenshot, it would be great! I am currently testing here, but I guess I need to upload a model to gdrive... |
Hey Seiji, theLastBen actually downloads the model automatically, but sure. Here is the log that I see in my colab while I wait, I will get a screenshot in a moment.
|
yeah, i was actually just trying this all myself; looks like it starts in the install script actually, it's not even finding launch.py??
filesystem wonkiness? i honestly never use colabs so i have next to zero familiarity with them... |
just out of curiosity i tried installing the dreambooth and dreamartist extensions to the colab and got very similar failures
kinda wondering if this is more of a general extensions vs colab thing |
Not sure, Tim. I am using aesthetic gradients successfully, web browser successfully, and Dynamic prompts. @zero01101 do you mind confirming if these 3 work for you? Just so we can see if we're on the same page? |
hah, google started yelling at me for going over my storage allotment so i kinda deleted my gdrive's SD and colab folders, let me spin those up again to check - assuming "web browser" is the image browser extension? |
Yep, it’s listed as web browser in the extensions tab.
…On Mon, Dec 26, 2022 at 6:46 PM tim h ***@***.***> wrote:
hah, google started yelling at me for going over my storage allotment so i
kinda deleted my gdrive's SD and colab folders, let me spin those up again
to check - assuming "web browser" is the image browser extension?
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4TQTDEMXJCHQ5F3JMUG6MLWPIU5BANCNFSM6AAAAAATJ42XLM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
From what you guys are describing we would only need to make our extension not have to run command line programs. [Edit] |
Also, yeah, I was using the wrong ipynb it seems. |
Worst case, we can use a try catch to catch import exceptions and just run it using |
If space is an issue I can share my models folder with you. Sd itself is a few gb, but it would at least clear it up a bit. |
no worries on space, thanks though :) dynamic prompts returned an error on install:
but otherwise does appear to run as expected... it's also the only one of the three with an
:badpokerface: uhhh i will take your word as gospel on that lol, i am still super noob re: all things python |
Updates app reference Signed-off-by: Victor Seiji Hariki <victorseijih@gmail.com>
@createperhaps give this new version of the extension a try |
No problem! Glad to help! But the thing is... I didn't do anything; the repo also has not changed since a day ago ; ) This is an issue that would affect only people who updated the extension in the ~4 hour time window I was writing the cache busting code, as those were the commits replaced with the branch force push. It seems it may also be transient, then! Still, the easiest and fastest way to get this fixed for now, if you have the problem, is to delete the extension altogether and reinstall it. |
This is odd-I didn't update when the error hit me. I also actually had the issue, and noticed I was behind, I thought the update may have fixed my issue. Alas, it didn't. |
...huh, so i thought that's specifically what
|
Guys in the extension tab keep getting {"detail":"Not Found"} error. How can ı fix? |
@cerarslan open devtools (F12) and run the following command: console.debug(document.getElementById("openoutpaint-iframe").src) If you copy-paste, the browser will not allow you to until you type whatever it is asking you to. I recommend you just type it out. Post here an screenshot of the result |
which platform ı have to use for devtools (F12) sir? |
Looks like chrome to me.
…On Sat, Dec 31, 2022 at 9:07 AM cerarslan ***@***.***> wrote:
which platform ı have to use for devtools (F12) sir?
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4TQTDDWV4VIC2OR442F773WQA4ZTANCNFSM6AAAAAATJ42XLM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@cerarslan devtools would just be in your web browser of choice, just push the f12 key on your keyboard. it's pretty universal between all of them. did you add the directory switch as shown in #11 (comment) ? for what it's worth, i've just spun up my gdrive copy of the colab with openOutpaint as the only installed extension and i'm not able to reproduce neither the |
When I got that issue though, it was because I didn’t use the CD. No disrespect to Ben, but he cd’d to web ui then cds back….I feel like I should have mentioned this hours ago lol
… On Dec 31, 2022, at 9:12 AM, tim h ***@***.***> wrote:
@cerarslan <https://github.com/cerarslan> devtools would just be in your web browser of choice, just push the f12 key on your keyboard. it's pretty universal between all of them. did you add the directory switch as shown in #11 (comment) <#11 (comment)> ?
for what it's worth, i've just spun up my gdrive copy of the colab with openOutpaint as the only installed extension and i'm not able to reproduce neither the .githooks/precommit weirdness, nor the {detail:not found} issue - however i did just consider that i'm not using the most up-to-date colab version at this point if ben updated it...
—
Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4TQTDFYA343FILJNFVFUFDWQA5OPANCNFSM6AAAAAATJ42XLM>.
You are receiving this because you were mentioned.
|
Maybe it is? I hadn't looked into the code more specifically when requesting that, so it may be that only people who have at some point checked out the testing branch are affected. From what I see from the command being run, it seems to indeed only fetch main head. |
Nay, I never got the test branch. |
@zero01101 I noticed just now that we ended up not adding anything to the README regarding the colab fix... I think we should add something there. |
|
guys sorry to bother you again but in extension tab (openOutpaint) I get ' openOutpaint init and colab side display openOutpaint init edit: When I just restart to ui, submodule path error is gone but I see still {"detail":"Not Found"} error on extension tab. |
Try deleting the whole extension from gdrive and reinstalling via webui |
Not working this time sir :/ |
Can you try doing this? |
And also, check if the %cd still is there. If you reloaded from thelastben's git it will have resetted. |
I always compare the latest version of TheLastBen with my own. Enable_API= TRUE and %cd check done. I also changed my lines in webui-user.bat and .sh to COMMANDLINE_ARGS="--api --cors-allow-origins=http://127.0.0.1:3456" this. When I write on devtools(F12) to console.debug(document.getElementById("openoutpaint-iframe").src) I get syntax error I guess. Btw I didn't copy paste. |
Oh, there are two ' in each side in yours. It must a single quote (') or a double quote (") in each side. '' Is different from " |
It's getelementbyid, you are missing the get |
Oh... Sorry, can you replace 'document' with 'gradioApp()'? |
No issues whatsoever, it was my mistake after all. Hm... I will be offline for some hours here... For now, an undefined src is an issue that I did not expect. Can you do it again but without .src? Also, I may ask you to join our discord for more help afterwards. |
Okay... If the iframe does not exist whatsoever we have a bigger problem in our hands. @cerarslan, can you enter in this discord? |
Oww, this is sad :/ . I'm in discord buddy |
Internal Server Error?
My guess is that is not yet implemented to run in colab notebooks but install flawlessly this thing looks great I wish I could use it inside colab too
The text was updated successfully, but these errors were encountered: