Skip to content
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

error generating images after upgrading from v0.6.0-pre to v0.6.1 #116

Closed
ssube opened this issue Feb 7, 2023 · 1 comment
Closed

error generating images after upgrading from v0.6.0-pre to v0.6.1 #116

ssube opened this issue Feb 7, 2023 · 1 comment
Labels
status/fixed issues that have been fixed and released type/bug broken features
Milestone

Comments

@ssube
Copy link
Owner

ssube commented Feb 7, 2023

When upgrading from one of the v0.6.0 pre-release versions to the v0.6.1 release, the new face outscale slider may not be set correctly, leading to a type error when sending the image request:

TypeError: Cannot read properties of undefined (reading 'toFixed')
    at appendUpscaleToURL (main.js:39132:68)
    at Object.txt2img (main.js:39197:11)
    at Object.generateImage [as mutationFn] (main.js:65986:35)
    at Object.fn (main.js:37436:33)
    at run (main.js:36694:33)
    at new Retryer (main.js:36739:5)
    at Mutation2.executeMutation (main.js:37431:22)
    at main.js:37399:22

Since the state version changed between v0.5.0 and v0.6.0, that should erase existing/invalid state when upgrading from v0.5.0, and I think this is only an issue when coming from one of the v0.6.0 pre-release builds.

Clearing the app data should work, as usual.

@ssube ssube added status/new issues that have not been confirmed yet type/bug broken features labels Feb 7, 2023
@ssube ssube added this to the v0.7 milestone Feb 11, 2023
@ssube ssube added status/fixed issues that have been fixed and released and removed status/new issues that have not been confirmed yet labels Feb 11, 2023
@ssube
Copy link
Owner Author

ssube commented Feb 11, 2023

I don't think this is happening when upgrading from v0.5.0 to v0.6.0, so I'm probably not going to add a migration unless that's also reported, but I have added a Reset All button to the client that will reset your local state. That will erase any prompts and parameters you have saved, but it should fix this error and similar ones.

@ssube ssube closed this as completed in 8f0a8e6 Feb 11, 2023
@ssube ssube mentioned this issue Feb 14, 2023
51 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/fixed issues that have been fixed and released type/bug broken features
Projects
None yet
Development

No branches or pull requests

1 participant