-
Sub-task
-
Resolution: Won't Do
-
Major
-
None
-
3.5
-
None
At the moment, the only feedback the user gets, is the number of tasks that have been executed, along with the eventual info, warn or error messages tasks would yield, and that's refreshed every 3 seconds.
One of the frustrating things is that sometimes a save() operation (which happens after each successful module install/update) can take more than a few seconds, thus no progress is seen. Would be nice to send some feedback to the user about this, either through the form a message ("currently saving...") or some progress bar (eventhough afaik we have no way of knowing the actual progress of a save operation)
Another thing which we need to handle properly are failing tasks and exceptions. At the moment, the page keeps on refreshing itself, even if the actual update mechanism has been interrupted. This should also help with having tasks which fail on purpose, for instance if a restart is needed.
- is duplicated by
-
MAGNOLIA-2067 Updater: feedback message implies job is done before it actually is
- Closed
- is related to
-
MAGNOLIA-1667 Updatemech : the whole process should be running in a separate thread
- Closed
-
MAGNOLIA-1670 Updatemech : review exception handling (loading and lifecycle)
- Closed
-
MAGNOLIA-2374 The title of the status page should be different when the update is complete and it is ready to start.
- Closed
-
MAGNOLIA-2598 Module dependency issue should be displayed in update ui
- Closed
-
MAGNOLIA-2109 Provide module status page
- Closed
-
MAGNOLIA-2673 update: error message should print the failing task's name and root cause
- Closed