Skip to content

[Feature]: Targeted Failure Remediation #103

Description

@abercrombiejc-cloud

What problem are you trying to solve?

It would be helpful for the user and support if when MHC is run again after one or more warnings or failures were found only the targeted failure(s) would be checked, saving time from re-checking all items. Here's a perfect example I experienced on my own Mac just today:

I ran MHC and it found two items to address: My Downloads folder files were taking up too much disk space; my Homebrew version needed to be updated. I cleaned out over 80 GB of data in Downloads and updated Homebrew to version 7.0.6 (the newest). I then re-ran MHC and everything came out healthy. But it had to check all 40 items before I knew this, when it would have been much more efficient to check only those two items.

Proposed behavior

A date-stamped log file could be created when MHC runs the first time noting the failed items so that the log could be consulted when MHC is run again to quickly identify what needs to be checked again.

Alternatives you have considered

Another option would be to have a button to re-check just the warned-about or failed item(s) on the Results Overview popped-up remediation window. (I don't remember the exact name now that I've resolved the issues on my Mac. Sorry!) But if the Results Overview is not intended to be left open an indeterminate amount of time that might not be a good idea. For "quick fixes" it would be, though!

Which part of the project would this affect most?

End-user dialog experience

Who benefits most?

Both

Anything else

In thinking about this, if this were implemented, there ought to be an initial query to the user when running MHC to ask how the user wants to run the check:

  1. Check items that failed or were warned about previously?
  2. Check all items?

For #1 only the "failure log" would be consulted to target just those items for the check. For #2 no log would need to be checked.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions