Hi all I'm wondering if reducing the amount of silent failures (something goes wrong, but no error is displayed) is something to focus on for ML++?
During install, a lot of problems happen unnoticed, because the results of install actions aren't always checked and considered blocking of failed. So if the next release cycle would include checks that block on significant errors, like network configuration finished, but no ip address is assigned to a device. But also applications that don't start from the GUI (whatever gui you use) without displaying an error (like executable not found or not executable). It would be a good idea to have automatic verification scripts to check whether a system is consistent. e.g. it should be relatively easy to check the menu with the filesystem if the executables are actually there and +x. just a thought... Cheers Simon
