Repository navigation
Vault from a newer MorphGate panicked upon running with old version of the app - #14
Merged
Merged
Conversation
Signed-off-by: Valentino Međimorec <valentino@medimorec.com>
Signed-off-by: Valentino Međimorec <valentino@medimorec.com>
Signed-off-by: Valentino Međimorec <valentino@medimorec.com>
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.
Vault from a newer MorphGate: say so instead of not starting
0.2.0 panicked at setup on a vault 0.2.1 had moved to schema 8, and
no window appeared. The refusal is now its own error (NewerVault,
not "corrupt"); the app starts without the vault and its window says
to install the latest version, leaving the vault as it is. Sync and
the rest don't start.
The AppImage e2e ends by raising the vault's schema and checking the
message and the untouched file. Docs: 8 migrations, version 0.2.1.