Samuel Dionne-Riel 00f81fa95c boot/init: Handle hung tasks ... The way we're handling them is to have a global timer that is reset at any point a task is ran. This gives a maximum amount of chances to any task to have its dependencies resolve. A minimum of 60s is given, but in reality the chances are the conditions for trying to resolve were already present before the timeout started counting towards that particular dependency. Note that a long running task, when successfully ran, does not cause the timeout to be reached. E.g. at 10s of timeout a task is started, the loop is not executed until the task exits. When it exits the branch followed is for a task that ran, which means that even if the task took 70s total (which gives us 80 seconds) a timeout of 60s wouldn't apply here. Though, please, don't make your tasks take that much time to run!		2020-11-07 20:13:31 -05:00
..
applets	boot/applets: Add key-held utility	2020-02-29 16:10:00 -05:00
error	boot/gui: Further fix applets for LVNanoSVG namespace change	2020-05-21 18:15:21 -04:00
init	boot/init: Handle hung tasks	2020-11-07 20:13:31 -05:00
recovery-menu	boot/recovery-menu: Add missing file	2020-11-06 16:30:22 -05:00
script-loader	boot/script-loader: Add mruby-zmq	2020-10-27 15:23:40 -04:00
splash	boot/splash: Allow textual questions to be asked	2020-11-07 19:22:33 -05:00