fix(gui): preserve disabled VAE tiling in configs#2346
Open
DilanRG wants to merge 1 commit into
Open
Conversation
Treat the presence of sdtiledvae separately from its truthiness so the documented zero value survives a launcher config reload. Fixes LostRuins#2065.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sdtiledvae: 0when loading a.kcppsfile in the launcherThis addresses the VAE tiling threshold reload bug in #2065. Zero is the documented value for disabling VAE tiling, but the previous truthiness check replaced it with the default.
Verification
koboldcpp.pysyntax compilation passes0, saved768, and a missing keygit diff --checkpassesThe existing
tests/test_koboldcpp.pydoctest still has one unrelated warning-text expectation failure on currentconcedo_experimental.