Display user-facing error messages for incompatible/out-of-date Tahoe-LAFS configurations#559
Merged
Conversation
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.
Recent changes in both Magic-Folder and ZKAPAAuthorizer have broken compatibility with older Tahoe-LAFS and Gridsync configurations: Specifically, the "magic-folder" feature present in earlier versions of Tahoe-LAFS has been removed as of Tahoe-LAFS version 1.15 (having been split off into a standalone project with a different configuration format), while ZKAPAuthorizer's newer backup/restore system has removed the older "v1" endpoints used by previous versions. Unfortunately, neither project has provided a migration path for converting an older configuration to a new one, thus leaving on-disk configurations that cannot be used with newer versions of the software.
This PR checks for such out-of-date configurations within the Gridsync configuration directory and, if found, displays a message to the user, explaining the compatibility-break and providing suggestions for how to continue.