save_pil_to_file function in webui makes it possible to serve a saved image without writing it to temporary directory. By appending the extra stuff to it, you're breaking that.

save_pil_to_file function in webui makes it possible to serve a saved image without writing it to temporary directory. By appending the extra stuff to it, you're breaking that.

You mean this? I noticed that register_tmp_file registers the saved file to gradio, which is exactly the location to be modified, and the path mounted by gradio will cause the gallery not to refresh after the file with the same name is saved.

The solution I had in mind was to add the question mark with time just before the image is served, not to the already_saved_as field, which would remain as a proper filename.

669b518

@AUTOMATIC1111 The Replace preview image functionality is also broken and looks like it needs a similar fix a3cdf9a.

I think unifying the address of gradio and file_obj can reduce some complexity to avoid confusion? The premise is that modifying gradio at the same time will not introduce more incompatibilities.

It also breaks "Save" button - either implementation. I reverted the change because this for sure will also break a bunch of extensions. There should be a better solution than this.

It also breaks "Save" button - either implementation. I reverted the change because this for sure will also break a bunch of extensions.

You mean the Save button under the gallery? It seems to work fine on my branch.

There should be a better solution than this.

In the final analysis, it is a problem caused by the browser's use of cache. I tried to insert no-cache but it didn't work. This is the only effective solution I found, and it is not difficult to be compatible. You only need to remove the characters at the end. If it What is broken can also be easily fixed, I don't know what extensions are affected by it.

I put it to you that this is not caused by browser cache:

1. change settings to always save image as a.png
2. make an image
3. make another image, observe that you get the same output as first time
4. open the image in a new tab, observe that a different image from first time appears
5. go back to txt2img and generate another image

The expectation after 5 if the browser cache is at fault is that the image will change to the the image produced in step 3, since it is what is in the cache currently. Reality is you'll still see the initial image from step 2.

I guess it is cache, the browser does not even make a request.

When I generate an image and then delete it to generate another, I can observe no change here.

But if you open in a new tab, it will be new, and devtools will still not change at this time.

The preview function seems to be broken, the preview image is cracked