Open AlexysLovesLexxie opened 3 weeks ago
@akx any insight
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
Corrupt download, delete and re-download is my best guess.
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
Corrupt download, delete and re-download is my best guess.
maybe you're right I assume that he's using the same known good file because he wrote
Scaler should have loaded and properly executed without error, as per previous versions (I was on 1.7.0 until recently).
I take this as fine 1.7 but in 1.8 when we switch to spandrel it stoped not working not sure now
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
Corrupt download, delete and re-download is my best guess.
I'm sorry, I guess I wasn't 100% clear.
This was tested on not one, but two installs of 1.9.3, done days apart. Logs are taken from a minutes-old, fresh, clean install, which I did in order to satisfy the The issue exists on a clean installation of webui
checkbox on my report. The two scaler files in question, 4xUltrasharp_4xUltrasharpV10.pt
and 4xNMKDSuperscale_4xNMKDSuperscale.pt
were copied directly from my 1.7.0 install, which is functioning correctly.
[EDIT] I do not know why it is even mentioning a zip file in the error log - the .pt
files aren't zipped, unless there is something I do not understand about the .pt
format?
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
Corrupt download, delete and re-download is my best guess.
maybe you're right I assume that he's using the same known good file because he wrote
Scaler should have loaded and properly executed without error, as per previous versions (I was on 1.7.0 until recently).
I take this as fine 1.7 but in 1.8 when we switch to spandrel it stoped not working not sure now
I skipped from 1.7.0 to 1.9.3 - doing a fresh install, not an update. Then to get the information for this report, I did another fresh, clean install. Copied the previously working .pt
files over from my 1.7.0 install.
Well, just working off the error message: If the .pt files are actually intact .pt files (i.e. zips) you should be able to rename them to e.g. 4xUltrasharp_4xUltrasharpV10.zip
and open them with your favorite archiver. Alternately, if you're on an UNIX system, file 4xUltrasharp_4xUltrasharpV10.pt
and/or zipinfo -l 4xUltrasharp_4xUltrasharpV10.pt
should show you what they actually are.
It's possible our earlier architecture had been happy loading files with the wrong extension.
F I think I found the issue
try rename the .pt
to .pth
btw I don't think 4xUltrasharp(ESRGAN) are zip files
Renaming the ,pt
files to .pth
worked a treat.
interestingly enough, renaming them to .zip and trying to open them was a no-go, even on re-download. but your fix actually fixed it. I will suggest to the uploaders of these files on CivitAI that they may want to update the file extension, unless you guys plan on changing the code so that they work as they used to?
cheers!
On Sun, Apr 28, 2024 at 8:43 AM w-e-w @.***> wrote:
F I think I found the issue try rename the .pt .pth
— Reply to this email directly, view it on GitHub https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/15650#issuecomment-2081525082, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6I5UHOTDR5DOYUPKJFDQCTY7UKJPAVCNFSM6AAAAABG42YYAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGUZDKMBYGI . You are receiving this because you authored the thread.Message ID: @.***>
Checklist
What happened?
Errors when trying to use
4xUltrasharp_4xUltrasharpV10.pt
and4xNMKDSuperscale_4xNMKDSuperscale.pt
.Steps to reproduce the problem
4xUltrasharp_4xUltrasharpV10
or4xNMKDSuperscale_4xNMKDSuperscale
from the dropdown menu.What should have happened?
Scaler should have loaded and properly executed without error, as per previous versions (I was on 1.7.0 until recently).
What browsers do you use to access the UI ?
Mozilla Firefox, Google Chrome, Brave
Sysinfo
sysinfo-2024-04-28-09-23.json
Console logs
Additional information
No response