Repository navigation
Sync: toast when it stops working - #40
Merged
Merged
Conversation
The TV PC's sync folder became read-only and every write failed for days without anyone noticing. Now a toast says so (once, with the reason), another says when it works again, and the log notes a repeated failure once instead of every 30 seconds.
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.
Since Oct 27 every sync write from the TV PC has failed ("The media is write protected" on
Q:\flex), thousands of times a day in the log, with nothing on screen.Tested: unit test for the notices; ran Flex with a scratch data folder and a read-only sync folder (toast shown), then made it writable (recovered within 30s, toast shown).