migration fixes - #411
Merged
Merged
Conversation
…ing template fields before final validation
…the whole wingman config
… template invariant
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
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.
Fixes several problems reported by a tester who updated from Wingman AI 2.1.1 to 3.1.6:
jump across several versions at once, changes got lost along the way and Wingman AI
silently fell back to factory settings — audio devices, voice activation, STT
configuration, everything. Updates now carry all your settings over correctly, no
matter how old the version you're coming from is.
used a custom skill that isn't installed on your PC (anymore), the entire config
refused to load. Now the missing skill is simply skipped with a warning and
everything else keeps working. Your settings for that skill are kept, so it comes
back as soon as you reinstall it.
or when no config was loaded.
Also fixed in the Client (ships with the same release): the on/off switches for
whispercpp, XVASynth and persistent memory looked enabled but were never actually
saved — which is why whispercpp kept turning itself off even after a successful
connection test.
If this bug already reset your settings: update, close Wingman AI, delete everything
> 2.1.1in%APPDATA%\ShipBit\WingmanAI, and start again — the update willre-run and restore everything from your old version.