[Bug]: No interface is running right now (local still working). Gradio team suggest to use version 3.18.1b7 (UI broken if updated)

ThanapatSornsrivichai commented 1 year ago

Is there an existing issue for this?

[X] I have searched the existing issues and checked the recent builds/commits

What happened?

Python 3.10.10 (tags/v3.10.10:aad5f6a, Feb 7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)] Commit hash: 3715ece0adce7bf7c5e9c5ab3710b2fdc3848f39

Gradio interface goes down after 3-4 hours showing No interface is running right now.

Local interface still working http://127.0.0.1:7860

The issue was reported in gradio github https://github.com/gradio-app/gradio/issues/3060 https://github.com/gradio-app/gradio/issues/3060#issuecomment-1435250754 Gradio team suggest to use gradio==3.18.1b7 but when I tried to use version 3.18.1b7 the UI got all messed up on all devices (all script menu shown without selecting it, wrong icon placement etc.) and inpainting was not working.

Is there a way to use/update the repo to gradio version with 3.18.1b7?

Steps to reproduce the problem

Start webui with share=True
30minute - 4hours the link ----.gradio.live will goes No interface is running right now.

Second scenario trying to use gradio 3.18.1b7

Set requirement to gradio==3.18.1b7
launch webui with share=True
UI is all mess up

What should have happened?

Gradio link should able to access up to 72 hours

Commit where the problem happens

3715ece0adce7bf7c5e9c5ab3710b2fdc3848f39

What platforms do you use to access the UI ?

Windows

What browsers do you use to access the UI ?

Google Chrome

Command Line Arguments

No

List of extensions

No

Console logs

No error

Additional information

No response

acheong08 commented 1 year ago

Occurs occasionally but not consistent

acheong08 commented 1 year ago

Note: I'm using fork with updated UI

ThanapatSornsrivichai commented 1 year ago

Note: I'm using fork with updated UI

Are you able to use webui with gradio version 3.18.1b7? May I have the fork? Thank you

acheong08 commented 1 year ago

Are you able to use webui with gradio version 3.18.1b7?

Haven't tried but after running it again, it was fixed for some reason

acheong08 commented 1 year ago

May I have the fork? Thank you

Original fork: https://github.com/anapnoe/stable-diffusion-webui

ThanapatSornsrivichai commented 1 year ago

Are you able to use webui with gradio version 3.18.1b7?

Haven't tried but after running it again, it was fixed for some reason

Which repo are you running from? the original fork or the v2 one. I'm having this issue for 2weeks now.

acheong08 commented 1 year ago

Which repo are you running from? the original fork or the v2 one. I'm having this issue for 2weeks now.

V2 via Google Colab

ThanapatSornsrivichai commented 1 year ago

Which repo are you running from? the original fork or the v2 one. I'm having this issue for 2weeks now.

V2 via Google Colab

Thank you, I'll try to it runs and see if the issue was fixed.

ThanapatSornsrivichai commented 1 year ago

@acheong08 The branch v2 webui works on local. Now I'm testing the share link duration. This is out of topic

The requirement file got conflict on fastapi==0.90.0 and 0.90.1 (I've changed to 0.90.1)
The style dropdown only limit to 8 styles. More than that, it doesn't show up.

acheong08 commented 1 year ago

I got an issue with fastapi 0.90.1 a while back. Might have been fixed recently

acheong08 commented 1 year ago

The style dropdown only limit to 8 styles. More than that, it doesn't show up.

I'll check this out. It should scroll iirc

anapnoe commented 1 year ago

@acheong08 The branch v2 webui works on local. Now I'm testing the share link duration. This is out of topic

The requirement file got conflict on fastapi==0.90.0 and 0.90.1 (I've changed to 0.90.1)

The style dropdown only limit to 8 styles. More than that, it doesn't show up.

use mouse wheel to scroll down the scrollbar is quite thin

ThanapatSornsrivichai commented 1 year ago

@acheong08 The branch v2 webui works on local. Now I'm testing the share link duration. This is out of topic

The requirement file got conflict on fastapi==0.90.0 and 0.90.1 (I've changed to 0.90.1)

The style dropdown only limit to 8 styles. More than that, it doesn't show up.

use mouse wheel to scroll down the scrollbar is quite thin

I've scrolled down but it just show the first 8 saved style. Maybe I'll try add it again on this repo. I copied the csv files from my last repo.

ThanapatSornsrivichai commented 1 year ago

@acheong08 3hours and the share link is down. local http://127.0.0.1:7860 still working but not the xxx41b3.gradio.live

anapnoe commented 1 year ago

@acheong08 The branch v2 webui works on local. Now I'm testing the share link duration. This is out of topic

The requirement file got conflict on fastapi==0.90.0 and 0.90.1 (I've changed to 0.90.1)

The style dropdown only limit to 8 styles. More than that, it doesn't show up.

use mouse wheel to scroll down the scrollbar is quite thin

I've scrolled down but it just show the first 8 saved style. Maybe I'll try add it again on this repo. I copied the csv files from my last repo.

click into the promp textarea and hit a couple of enter keys to grow large enough and then click on the styles above to see if more than 8 lines are shown (I will fix the cropping issue by increase the z-order) also can you share some more info (platform and browser) i check it on chrome and mozilla win10 and it works as expected do you see the scollbar on the right or it is not there at all i havent tested on edge safari.

mozilla mozilla chrome chrome

nom commented 1 year ago

This is a gradio issue: https://github.com/gradio-app/gradio/issues/3060. It's fixed on the gradio side with gradio==3.19, however the AUTOMATIC1111 webui CSS does not play well with this version.

ThanapatSornsrivichai commented 1 year ago

This is a gradio issue: gradio-app/gradio#3060. It's fixed on the gradio side with gradio==3.19, however the AUTOMATIC1111 webui CSS does not play well with this version.

That's what I'm trying to say. They probrably won't upgrade to 3.19. I don't know why no one having problem with gradio link goes inactive after a while. I got 100% rate across multiple device and os.

Osiris554 commented 1 year ago

I've been using the GitHub install and having this issue for about 2 months after February. Yesterday I removed the --medvram argument and my remote interface has been running for 26 hours with out the link expiring, or "No Interface Running" error

caleboleary commented 1 year ago

This CSS fixed most of the issues for me when I upgraded to 3.19.1, though inpainting appears to break and I haven't fixed that, posting in case anyone takes up upgrading gradio


.hidden {
    display:none;
}

.token-counter {
    width:30px;
    min-width: 30px;
    max-width: 30px;
}

div.svelte-362y77>*, div.svelte-362y77>.form>* {
   min-width:0;
}

martinzhanggz commented 1 year ago

This CSS fixed most of the issues for me when I upgraded to 3.19.1, though inpainting appears to break and I haven't fixed that, posting in case anyone takes up upgrading gradio
.hidden {
    display:none;
}

.token-counter {
    width:30px;
    min-width: 30px;
    max-width: 30px;
}

div.svelte-362y77>*, div.svelte-362y77>.form>* {
   min-width:0;
}

may I ask, where should I insert such magnificent codes?

caleboleary commented 1 year ago

@martinzhanggz

Create user.css at the same level as webui.bat

martinzhanggz commented 1 year ago

@martinzhanggz

Create user.css at the same level as webui.bat

thanks for your lovely help~~

ImpulseMirror commented 1 year ago

This is a gradio issue: gradio-app/gradio#3060. It's fixed on the gradio side with gradio==3.19, however the AUTOMATIC1111 webui CSS does not play well with this version.

That's what I'm trying to say. They probrably won't upgrade to 3.19. I don't know why no one having problem with gradio link goes inactive after a while. I got 100% rate across multiple device and os.

Is the consensus that we have to just fix this on our own because the official team has no interest in applying the fix?

kaibosh99 commented 1 year ago

How do I force an update to gradio? I thought changing the version in the requirements' files and doing a 'git pull' would do it, but...

KillfootNJ commented 1 year ago

How do I force an update to gradio? I thought changing the version in the requirements' files and doing a 'git pull' would do it, but...

requirements.txt and requirements_versions.txt both need set gradio==3.19.1 then open webui.bat it well auto update to 3.19.1. that is how i solve it.

kaibosh99 commented 1 year ago

Okay, so if I update gradio and drop in the user.css patch, then the gradio link will go back to being reliable - but at the cost of the 'Training' tab still being screwed up style-wise? Because I am treading a little too deep into the pool here, I am very leery of patching a weird semi-fix if it means breaking other stuff (possibly permanently?).

I'm okay with keeping track of what I've done, on the assumption that I can 'unpatch' when I want to use the training tab... I noticed that WebUI updated though (did a git pull just now), and I worry that a patch like this will already break something, as it was created on a different version. Can anyone help explain why or why not I need to worry about this?

Is it just me or does it seem strange that this bug hasn't been fixed? From what I understand someone just needs to tidy up the style code for the interface, so it will work properly with the newer version of gradio? I would have thought all kinds of people would be using this remote server feature, which to me is incredibly handy.

ThanapatSornsrivichai commented 1 year ago

This CSS fixed most of the issues for me when I upgraded to 3.19.1, though inpainting appears to break and I haven't fixed that, posting in case anyone takes up upgrading gradio
.hidden {
    display:none;
}

.token-counter {
    width:30px;
    min-width: 30px;
    max-width: 30px;
}

div.svelte-362y77>*, div.svelte-362y77>.form>* {
   min-width:0;
}

It would be great if there any fix for inpainting. I mostly use inpainting :(

caleboleary commented 1 year ago

This CSS fixed most of the issues for me when I upgraded to 3.19.1, though inpainting appears to break and I haven't fixed that, posting in case anyone takes up upgrading gradio
.hidden {
    display:none;
}

.token-counter {
    width:30px;
    min-width: 30px;
    max-width: 30px;
}

div.svelte-362y77>*, div.svelte-362y77>.form>* {
   min-width:0;
}
It would be great if there any fix for inpainting. I mostly use inpainting :(

I did some poking around and it seems like the image component takes more parameters in the new version of gradio so the backend needs to be updated to match the new shape, and I'm no good at python haha. So the inpaint won't be a CSS fix if I have understood correctly.

kaibosh99 commented 1 year ago

Thanks a lot. Hope this gets fixed sometime, the remote client feature is super cool and a handy toy to lend to friends.

Zephalon commented 1 year ago

This is not yet resolved. I started it before going to work at 7:30 am and around noon it broke. When I came home it worked fine on my PC.

Latest version with Gradio 3.23.

dyn-do commented 1 year ago

I am using Stable Diffusion WebUI with Gradio v3.24.1, but it occurs every time img2img is executed through WebAPI about 10 times. The WebUI is displayed with a local address. Is there any workaround?