My position hasn’t changed, see the last message 
I’m in favor of displaying contextual error messages in the right places (even showing the raw error when the error is unknown), but displaying the complete logs isn’t really Gladys’ philosophy.
Today in Gladys the topic has evolved a lot since we now have 2 patterns for surfacing errors in the interface:
-
When you’re in Gladys and you perform a « direct » action (add a camera, click a button, switch tabs, etc..), and there’s an error, we display the error in a blue/green/yellow/red badge depending on severity. Classic!
-
When a background task fails, we display the background task’s status and the error message in the « Background tasks » tab in settings:
Example of an error:
Now, this tab isn’t yet applied to all background tasks; the idea would be to add everything that runs in the background (scene execution, Gladys startup, etc..), so we can debug more easily.