Disable sync progress indicators #131
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.
Due to persisting bugs in tahoe's magic-folder status queue (which often displays inaccurate information or otherwise fails to reflect the number or state of queued upload/download operations), this PR (temporarily?) disables sync progress indicators from being displayed in the UI. Users needing to get a (very) rough sense of sync progress can still do so by watching the "size" status column (which increases as new files finish uploading), the newly-added "History" tab (which populates as files are added, updated, or removed), or the debug log (which now periodically prints the total progress and time remaining values as calculated from the magic-folder queue).
Proper status indicators will be re-implemented if/when the corresponding magic-folder bugs are fixed upstream (and/or when I figure out a sufficiently reliable workaround..). See #132