address Monterey changes causing TimeMachineProgress to error #266
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.
I noticed after I upgraded to Monterey (12.2 or 12.3, not sure when it started) that TimeMacineProgress would sometimes appear to get stuck at the (prep) stage. That was being caused by an error - apparently
tmutil status
now reports intermediate phases that lack any Percent value. This PR addresses that error, bumps the version, and as a bonus provides a little more info in the (prep) tooltip during the various backup phases provided by the apparently modified tmutil's status results.FWIW TimeMachineProgress's percentage stops advancing when TimeMachine goes into its 'cleaning up' phases, prior to 'stopping'. Addressing that is a separate issue that I'm not sure is worth the effort. I'm happy to try to help if you think it is.
Below is an example of the tmutil status data that triggers the stack dump: